13 ms·
Yeah its kind of sad that we still have to use node and java with better options out there. Don't get me wrong, Typescript, Deno, JVM, etc.. are all doing their
by Xeoncross 4y ago
Yeah its kind of sad that we still have to use node and java with better options out there. Don't get me wrong, Typescript, Deno, JVM, etc.. are all doing their best to right those ships, but it's would still be better to just scrap that stuff for a better foundation.
That is what everyone knows,
so that is what's taught,
so that is what everyone knows,
so that is what's taught.
I'd gladly onboard projects to Erlang, Rust, Zig, Go, or anything modern. Would save our planet so much wasted energy.
- moomoo11 4y agoThe problem is that our industry democratized to the point that people want to hire the cheapest resources who can ship something. A mediocre node or ruby developer costs peanuts to hire compared to one who is mediocre at Go or Erlang. Btw.. If you hire a mediocre go or Erlang developer you’re fucked. For IO bound work there’s not much difference between a service built with Go or Node. It’s really when you need services that have soft/hard real-time requirements or continuous processing requirements that imo it’s necessary to hire the right people for the right stuff. For anyone else who is making a web platform that doesn’t have much complex backend processing, they can just use ruby or node. Personally I use Go for all backend tasks and node for any one off scripting work. Go spits out a binary I can run on any Linux based system. Node scripts are easy to write and I use them for fixing issues or for simple single responsibility tasks.
- hot_gril 4y ago> The problem is that our industry democratized to the point that people want to hire the cheapest resources who can ship something This doesn't sound like a problem to me.
- hot_gril 4y agoDoing high-level stuff in those languages takes longer even if you know what you're doing, though.