Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Deno in 2023

deno.com

Post reply on HN
Print view View original

31–40 of 235 posts

Re: Deno in 2023

#31

Post by qprofyeh »

vorticalbox wrote: post #24
rtcode_io wrote: post #3

Deno 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.

They’re operating like a startup, which like you say should be perfectly fine. Can’t pretend like a giant when you don’t have the bank account for that.

Though they’re also selling a developer ecosystem. A lock-in. Are you willing to bet your company’s own software tools on a vendor that could go bankrupt from their other (hosting) business? The question is if Deno hosting dies, will Deno as a platform still thrive?

Re: Deno in 2023

#33

Post by willsmith72 »

vorticalbox wrote: post #22
tarruda wrote: post #17

Earlier 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

that feels like a really weak value prop to me. how often do you have to install that stuff? how hard is it actually? can you really not use, e.g. for react, the typical vite starter and it's done?

Re: Deno in 2023

#34

Post by rob74 »

ehhthing wrote: post #14
tarruda wrote: post #7

What is the state of Deno's node.js compatibility when compared to Bun?

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...

OTOH the ways that you can improve upon node's shortcomings while staying compatible with it are limited. Bun is taking the pragmatic approach of providing fast drop-in replacements for node, npm and other standard tools, while Deno was the original creator of node going "if I started node today, what would I do differently?". So, different approaches...

Re: Deno in 2023

#35

Post by ihateolives »

ecmascript wrote: post #27

I 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 envi…

OTOH Deno can produce self-contained binaries. For me this is a plus, it makes distribution so much easier. I don't care if it's 100MB, I just want to have one file which I can throw on my server,

Re: Deno in 2023

#36

Post by dingdingdang »

Would love to see the compile situation fixed - the generated executables are ~90MB+ at this stage and do now allow compression without erroring out. Deploying ala Golang is not feasible at that level but could well be down the line if this dev branch is picked up again!

The exe output grew from from ~50MB to plus ~90MB from 2021 to 2024: https://github.com/denoland/deno/discussions/9811 which mean Deno is worse than Node.js's pkg solution by a decent margin.

Re: Deno in 2023

#39

Post by ffsm8 »

smokel wrote: post #29
MadSudaca wrote: post #26

I 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 migh…

> If people were to use proper arguments to select technology, we wouldn't be in this mess in the first place.

The ultimate killer argument is always "does it improve my CV?"

CV driven development is usually the reason for questionable technology choices

Re: Deno in 2023

#40

Post by tarruda »

willsmith72 wrote: post #33
vorticalbox wrote: post #22

Earlier quoted context omitted.

> 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

that feels like a really weak value prop to me. how often do you have to install that stuff? how hard is it actually? can you really not use, e.g. for react, the typical vite starter and it's done?

It is more a matter of trust than effort, eg being less exposed to supply chain attacks.
Post reply on HN