Ask HN: Does anybody else is disenchanted with some languages ecosystems?
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?
12 comments
[ 5.0 ms ] story [ 41.5 ms ] threadDeno 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/
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.
The main problem is that we spent more time doing trial-and-error than actually developing software.
Maybe it was a bad choice, yes.
Maybe C# would be a better fit?
Thanks for your advice!
C#, Java, and to a lesser extent NodeJS and Python are enterprise level backend languages with support for whatever you can imagine.