Soremwar

12 ms·

1.
by Soremwar 4y ago
That new bench reporter is really something to look at
2.
by Soremwar 5y ago
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
3.
by Soremwar 5y ago
"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
4.
by Soremwar 5y ago
Hence why developers always recommend to use immutable sources when importing modules
5.
by Soremwar 5y ago
They don't though. They transpile it behind the scenes
6.
by Soremwar 5y ago
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 libr
7.
by Soremwar 5y ago
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
8.
by Soremwar 5y ago
Not that simple of a comparison since "data centers" mean a different thing in both cases
9.
by Soremwar 5y ago
You don't need to test a feature that they don't have
10.
by Soremwar 5y ago
Wrong, 1.0 released exactly one year ago, before there was mostly destabilization of the runtime and not really development features
11.
by Soremwar 5y ago
We may have WebGPU powered desktop applications in the near future though. Let's see how things play out, as you daid
12.
by Soremwar 5y ago
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
13.
by Soremwar 5y ago
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&#x
14.
by Soremwar 5y ago
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
15.
by Soremwar 5y ago
No they can't, Deno is JavaScript compliant
16.
by Soremwar 5y ago
For frontend TypeScript I assume you mean TypeScript that doesn't use JS modules but extensionless modules, the TypeScript folks sadly have decided to not bring compatibility here ATM.
17.
by Soremwar 5y ago
You do something like this export * as Oak from "https://deno.land/x/oak/mod.ts"; export * as Postgres from "https://deno.land/x/postgres/mod.ts"; Then you do th
18.
by Soremwar 5y ago
Yeah, libraries can't use import maps because import maps are not extensible
19.
by Soremwar 5y ago
You don't ever lose productivity or knowledge on a tool when a new one comes out though. A new thing that people like becomes popular and people start using it, old one becomes less used but it doesn't dissapear. You only really &
20.
by Soremwar 5y ago
They had to remove it from the Deno build process so Deno internals didn't need a compiler. However TypeScript support remains untouched and receives constant updates
21.
by Soremwar 5y ago
This. I cannot stress how important is this for modern app development. Just like Deno doesn't trust any script that is passed to it, no user should trust an app just cause it's installed directly in the system (and I can't b
22.
by Soremwar 6y ago
What link?
23.
by Soremwar 6y ago
The thing is that without read/write or net permissions, a malitious script that turns your computer into a mining rig will throw because it can't connect to any server or use your filesystem. We already expose CPU to third party
24.
by Soremwar 6y ago
Already fixed
25.
by Soremwar 6y ago
No matter if you are interested in Deno or not, seeing this amount of features in a year alone gives you an idea of what's to come for Deno in the future
26.
by Soremwar 6y ago
The catch is that it works in a case by case basis. The most used libraries are there and work wonders, but things like the Vue compiler won't work with NPM transformations and are better off with a native port, like VNO
27.
by Soremwar 6y ago
Actually that is being worked on (std/node is a shim for Node libraries that aims to make Node ecosystem 100% usable from Deno) but the idea is to build software with Deno's mindset and features on top of it. Just look at this Vue
28.
by Soremwar 6y ago
Fundamentally, Deno works way more like the language JavaScript is meant to be according to the vision of the ECMA committee (the ones who add features to the language). Problem is that a lot of software was built upon areas where Node devi
29.
by Soremwar 6y ago
What's even the point of using Go? If it's for static typing Rust has that So what's the benefit? Same can be said about any language really, it's personal preference
30.
by Soremwar 6y ago
Whot? How is that even comparable? It's third party code after all, the same happens when you use a library in any other language

More ›