Soremwar

That new bench reporter is really something to look at

Tracking where open resources like timers were invoked is something that is quite literally a game changer

People sleep on how good the Deno test runner is, but I can't for the life of me stress enough how many times the resource leak feature has saved my ass (developer of x/postgres)

"Immutable" in the sense that packages can't be taken down or modified by authors

If you wanna take it a step further, you can always opt in to that lock file with various degrees of strictness as you yourself mentioned

Hence why developers always recommend to use immutable sources when importing modules

They don't though. They transpile it behind the scenes

They are different, currently no Deno registries have dynamic version resolution (no greater than operator). Once you have locked in on a version you are in it for good unless you change it manually

However if the argument is: updating libraries break stuff, that is gonna happen every time in every language. There is no guarantee the next version will just work as the last one did

Reimplement in the way that they change certain rules to accommodate a more "modern JS" feel

And they absolutely use TS for the std library, just not in the runtime itself

Not that simple of a comparison since "data centers" mean a different thing in both cases

You don't need to test a feature that they don't have

Wrong, 1.0 released exactly one year ago, before there was mostly destabilization of the runtime and not really development features

We may have WebGPU powered desktop applications in the near future though. Let's see how things play out, as you daid

There have been multiple test runners built on top of Deno's vanilla testing (through the JSON output feature), those may fit your use case better

The current multi threaded and module isolated model however I think it's good for the great majority of projects, so I'm glad it's built in

IMO this is a terrible idea.

If I have learned anything from working long time with NPM is you can't trust a single command with updating your dependencies and you can't trust developers to respect semver on the long run.

I can't stress how many times I had to review and undo automated dependency bumps because my app suddenly stopped working, and the times I was forced to I had to bump said dependencies in the lock file myself

In a compiled language, where code is compiled once and valid there 'til the end of times this is not even a problem. In an interpreted language where all code is evaluated every time you run your program, this makes automated dependency management an impossible task

Only if you update dependencies, a fresh install would not have such integrity checks, so it's just as vulnerable as Deno hosts to such attacks

No they can't, Deno is JavaScript compliant