3 ms·
> Some years later, when I finally got around to learning and using Node.js, I realized just how poor the async/await/promise design Node.js was (error-prone by
by mhink 3y ago
> Some years later, when I finally got around to learning and using Node.js, I realized just how poor the async/await/promise design Node.js was (error-prone by design). But I highly doubt I would convince anyone to really give Elixir or Erlang a go.
IIRC Elixir got a pretty big boost early on thanks to folks making the jump from Rails to Phoenix, so it could kinda be the case that most of the folks who *would* give it a shot *have already* given it a shot.
That being said, I have the impression that you'd have more success with folks using Node.js than you might think. I expect there would be more pushback from folks using, say, Golang and Java... if only because the wider dev community doesn't look down its collective nose at those languages quite so much. (Unless you're talking about generics or null values, respectively!)
- hosh 3y agoI have tried with people using Nodejs. I didn’t really get much anywhere. The wall I run into starts with, “what do you think of Typescript?” I don’t try very hard though. At most, I put out feelers and see where it goes, because it is impractical for my team to switch to Nodejs. Due to the nature of the work, Python is a better choice for the team even if I think Elixir can still work better for me.
- zeroc8 3y agoGolang/Java/C++/Javascript developer here. We do look down our collective nose. I've tried to get into Erlang and I'm a big fan of Joe Armstrong. Erlang incorporates great ideas, but using it for a project seems a bit risky, since it is quite different from other mainstream languages. Go is more conservative, but less risky. It's just a C for today's world. I've had lots of success using it, even though I'm aware of its warts (especially when it comes to concurrency). That said, I'm kind of excited about Gleam. Let's see how that works out.
- gregors 3y agoI completely disagree with you that Go is a C for todays world. Rust/Zig/Carbon is a C for today's world, Go is much closer to the new Java/C# It's also good to remember Go itself wasn't always risk free though, every new tech has growing pains. https://www.kickstarter.com/projects/2066438441/haunts-the-manse-macabre/posts/373466 https://www.kickstarter.com/projects/2066438441/haunts-the-m... https://www.kickstarter.com/projects/2066438441/haunts-the-manse-macabre/posts/420311 https://www.kickstarter.com/projects/2066438441/haunts-the-m... The warts with respect to concurrency? That's the one thing Go does well! The real warts are associated with error handling.