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

Deno 2.8

deno.com

Post reply on HN
Print view View original

71–80 of 193 posts

Re: Deno 2.8

#71

Post by VerifiedReports »

hollowturtle wrote: post #49
Curosinono wrote: post #41

I don't get it why the hell is TypeScript still not nativly supported in modern browsers?

Because "it doesn't exist". It's just a layer on top of js, it doesn't have its own runtime, and btw what would supporting ts a the browser level mean? If you want to support a static typed language then you could just compile it down to wasm, if you just want to support types and ignore them at runtime there's an overhead price to pay, or should do runtime type checking? And with which tsconfig? Strict or not?

All good questions. But... it would simply eliminate a step and result in a single language.

Python supports types and is interpreted, right?

Re: Deno 2.8

#72

Post by yoyohello13 »

dan_rock_wilson wrote: post #26

Deno: has a basic permission model that is very helpful, written in Rust, and native TypeScript support. I'm not deep in the webdev / node / Bun ecosystems, I've just been a happy user of Deno for small services for several years. Can someone explain why it sounds like there's such rapid growth of Bun? Is it just being used as a bundler, but not as JS runtime? Just the permission system alone (though I wish it extend…

Same, I'm mostly a back end dev but when I dip my toes into frontend for personal projects Deno just seems like the most sane choice. It's really nice to work with. I'm kind of sad it doesn't seem to have taken off among the JS folks.

Re: Deno 2.8

#73

Post by yoyohello13 »

Curosinono wrote: post #41

I don't get it why the hell is TypeScript still not nativly supported in modern browsers?

My gripe is why doesn't Webassembly fully support dom manipulation. If we got that working anyone could just bring any language to the browser and we would finally be free from the shackles of JS.

Re: Deno 2.8

#74

Post by pjmlp »

ale wrote: post #27
pjmlp wrote: post #22

Earlier quoted context omitted.

As someone that works in projects with standard IT tools, not supporting NPM made it a non starter for us. No way it would go through standard build pipelines, or team skills.

"standard" IT tools?

Yes, IT from customer, or agency delivery operations, dictates what are the official tools in specific projects, including 3rd party dependencies in internal repos, and CI/CD is cut off from accessing public Internet.

Re: Deno 2.8

#75

Post by pjmlp »

afavour wrote: post #69
pjmlp wrote: post #22

Earlier quoted context omitted.

As someone that works in projects with standard IT tools, not supporting NPM made it a non starter for us. No way it would go through standard build pipelines, or team skills.

Oh, for sure. But I'm old enough to remember when standard IT tools would have never supported Node in the first place and the idea of JS on the server made everyone scream. You just need to build demand for that support.

For us the demand is, does it run everything that either Angular or Next.js require, or the SDKs from headless SaaS products.

Re: Deno 2.8

#76

Post by satvikpendem »

dmit wrote: post #52
dan_rock_wilson wrote: post #26

Deno: has a basic permission model that is very helpful, written in Rust, and native TypeScript support. I'm not deep in the webdev / node / Bun ecosystems, I've just been a happy user of Deno for small services for several years. Can someone explain why it sounds like there's such rapid growth of Bun? Is it just being used as a bundler, but not as JS runtime? Just the permission system alone (though I wish it extend…

> Can someone explain why it sounds like there's such rapid growth of Bun? In my case, when I start a little Typescript side project, instead of drowning in the sea of npm/yarn/berry/pnpm/bubble/vite/webpack/rollup/rolldown/rollout/swc/esbuild/teatime/etc I can just use one thing. And yes, only some of those are Pokémon moves and not actual tools from the JS/TS ecosystem.

But...Deno also has an all in one CLI too. The question was why Bun specifically grew in popularity over Deno.

Re: Deno 2.8

#78

Post by satvikpendem »

VerifiedReports wrote: post #64
vorticalbox wrote: post #55

Earlier quoted context omitted.

I think the main issue was when deno first came out it used urls for imports then later added support for npm. By then bun was already a thing and just ate into its share.

Why do you consider URLs a problem?

Annoying to update instead of a package.json, which they now have an equivalent of, realizing their mistake.

Re: Deno 2.8

#79

Post by TeriyakiBomb »

vmsp wrote: post #11
TingPing wrote: post #8

Earlier quoted context omitted.

> Plus, bought by Anthropic. Who thinks this is a positive?!

That wasn't a value judgment on the acquisition. I was just pointing out that it made the project more sustainable.

It really doesn't. You think Anthropic will still be in business in 10 years? If they are, it's not likely they'll be in the same shape.

Re: Deno 2.8

#80

Post by vorticalbox »

VerifiedReports wrote: post #64
vorticalbox wrote: post #55

Earlier quoted context omitted.

I think the main issue was when deno first came out it used urls for imports then later added support for npm. By then bun was already a thing and just ate into its share.

Why do you consider URLs a problem?

I don’t consider them a problem at all. It’s how browsers have worked for a long time.

My point was at the time when deno came out it was completely different to node with its imports and that meant a lot of existing packages just didn’t work out of the box. That just slowed its traction.

Personally I would have like deno it stick with url imports and not added the npm support.

Ryan set out to “fix” his mistakes with node only to fully embrace them again.

Post reply on HN