You can join the waitlist in the sneak peak of JSR linked in the end of the article: https://jsr.io/waitlist I'm curious on what the Deno team is building here.
Hmm, curious too. Maybe, given the few hints, an alternative to npmjs.com registry.
Deno in 2023
21–30 of 235 posts
Re: Deno in 2023
#22Earlier quoted context omitted.
Deno wasn't originally designed to be node compatible, but I think they realized nobody would want to switch to it because node is so prevalent already...
I think the main appeal of projects like Bun and Deno is the built-in tooling for building/bundling modern typescript applications without requiring dozens of dependencies for even a basic hello world app. If node.js decided to include functionality similar to what is available on Bun/Deno, both projects would probably lose traction quickly.
> If node.js decided to include functionality similar to what is available on Bun/Deno, both projects would probably lose traction quickly.
I believe this too. The big appeal for me is not having to install typescript, eslint, jest AND then set up all the configs.
deno has nice defaults, though the importing via URLS and browser compatible API do make deno very tempting
Re: Deno in 2023
#23You can join the waitlist in the sneak peak of JSR linked in the end of the article: https://jsr.io/waitlist I'm curious on what the Deno team is building here.
I assume it's an npm competitor? Likely with a different technical design.
Re: Deno in 2023
#24Deno Deploy dropped from 35 GCP regions to just 12: https://news.ycombinator.com/item?id=39127598
sure but is that a bad thing? this regions probably see next to or zero use and cutting them frees up money to be used on other things.
Re: Deno in 2023
#25Earlier quoted context omitted.
Deno wasn't originally designed to be node compatible, but I think they realized nobody would want to switch to it because node is so prevalent already...
I think the main appeal of projects like Bun and Deno is the built-in tooling for building/bundling modern typescript applications without requiring dozens of dependencies for even a basic hello world app. If node.js decided to include functionality similar to what is available on Bun/Deno, both projects would probably lose traction quickly.
Being an old dog in the prairie, I see the outcome of these projects being like egcs, and io.js.
They create some riff, make the key incumbent improve itself, and then the world moves on as if nothing happened.
Re: Deno in 2023
#26I know it sound silly but I love the aesthetic behind Deno's brand, it makes me want to use it for one project or another. Node.js is so old now. it's reliable but boring. I want something new, bold, and daring. Node.js is not it, although it was ~11 years ago. It's interesting how our views change.
Re: Deno in 2023
#27I have a deno app in production and it is working just fine. However, I still think node is superior when you self host when you are not using docker. Deno afaik still doesn't support any way of running one process for every CPU like the cluster module in Node.js.
I like to run my shit on the metal and without Docker and it feels like Deno was designed to run on Docker or some other kind of virtual containerized environment.
However, you can run it on node thanks to pm2, but I guess why even run on Deno in the first place?
Re: Deno in 2023
#28Earlier quoted context omitted.
I think the main appeal of projects like Bun and Deno is the built-in tooling for building/bundling modern typescript applications without requiring dozens of dependencies for even a basic hello world app. If node.js decided to include functionality similar to what is available on Bun/Deno, both projects would probably lose traction quickly.
> If node.js decided to include functionality similar to what is available on Bun/Deno, both projects would probably lose traction quickly. I believe this too. The big appeal for me is not having to install typescript, eslint, jest AND then set up all the configs. deno has nice defaults, though the importing via URLS and browser compatible API do make deno very tempting
Except they are playing catch up with what Microsoft says Typescript is supposed to mean.
I rather have pure JavaScript, or use the Typescript from source, without having to figure out if a type analysis bug is from me, or the tool that is catching up to Typescript vlatest.
Re: Deno in 2023
#29I know it sound silly but I love the aesthetic behind Deno's brand, it makes me want to use it for one project or another. Node.js is so old now. it's reliable but boring. I want something new, bold, and daring. Node.js is not it, although it was ~11 years ago. It's interesting how our views change.
This does indeed sound silly. If people were to use proper arguments to select technology, we wouldn't be in this mess in the first place. Unfortunately, most of us are more susceptible towards aesthetics, novelty, and admiration of self-proclaimed software gurus. Thanks for being open about this and sharing.
It would have been nice if I had realized this aspect of technological evolution earlier in my career. I might have spent more time learning about marketing than about the actual technology.
Re: Deno in 2023
#30I know it sound silly but I love the aesthetic behind Deno's brand, it makes me want to use it for one project or another. Node.js is so old now. it's reliable but boring. I want something new, bold, and daring. Node.js is not it, although it was ~11 years ago. It's interesting how our views change.
I'm not sure if this is real or a subtle parody of the stereotypical JS/node user.