Ask HN: Does anybody else is disenchanted with some languages ecosystems? | Hacker News Reader

Ask HN: Does anybody else is disenchanted with some languages ecosystems?

6 pointselnatro10 comments

Some weeks ago I started learning demo at my work. Their built-in support for Typescript and being developed in Rust seemed to be its strong points.

Now, there is no actual codebases I can look into, SQLite driver is broken, there are several ORMs that looked interesting but all of them are deprecated (I chose sequelize with MySQL), I’m also having disconnection errors when trying to do integration tests…

I feel discouraged and wonder if I’m a bad engineer (maybe that’s the problem) or deno is still in experimental phase.

Have any of you regretted choosing a cool technology? Did you used a different one or persevered with your decision? How did you keep working with that technology?

View on HN

Node JS and by extension Deno is built on a house of cards.

Deno is simply not ready for production. You can import NPM modules, but they aren't guaranteed to work.

https://docs.deno.com/runtime/manual/node/

So when is this going to change? I mean, I suppose deno will become mature at some point, right? How did other languages become mature?

It might never be ready for production.

Who picked Deno at your company? It's a odd choice given it's limited support.

Even if it's fine for some use cases, it sounds like a poor fit for your needs.

Well the idea was to use a typescript-capable environment, and we thought that deno could be a good fit.

The main problem is that we spent more time doing trial-and-error than actually developing software.

Maybe it was a bad choice, yes.

I think if I was in your shoes I would have evaluate what your ultimate goal is. Do you need a back in language with types ?

Maybe C# would be a better fit?

Thanks I’m thinking about golang, I don’t know we will see.

Thanks for your advice!

Golang is more mature, but it's still a relatively new language.

C#, Java, and to a lesser extent NodeJS and Python are enterprise level backend languages with support for whatever you can imagine.

If you don't need NPM modules, Deno is pretty nice. There's a Deno specific ecosystem (e.g. DB drivers) that is working fine, but of course you're limited compared to the huge NPM ecosystem.

Deno added Node compatibility later on. So while Deno itself (JS which is V8 anyway and the native Deno APIs like http) is probably stable (it is used as serverless runtime, e.g. from Supabase, of course Deno itself and Netlify IIRC), the Node compatibility is the problem here. Yeah, this is frustrating. Now we have Bun which tries to be a drop in replacement for Node. It you need NPM modules, you should probably just use Node. Or some other language.

I'm not, but am looking forward to everyone getting disenchanted with Go so I stop seeing yet another startup pick it for something it's bad at and then struggle to eke out performance and scale the project.

Reply on news.ycombinator.com