3 ms·
I cant answer for keithwhor I think websocket support is a huge + for picking nodejs. Lately rails got their socket support, and python3 has been getting bette
by dev360 11y ago
I cant answer for keithwhor I think websocket support is a huge + for picking nodejs.
Lately rails got their socket support, and python3 has been getting better support through async, but in both those languages, I've long felt its been pretty experimental, and there simply hasnt been a performant option available that has a good opinionated framework.
Nodejs has performance going for it at least if you look at the language benchmarks, and now with ES6, it feels like the language is finally starting to shape up.
- keithwhor 11y agoNodal doesn't have built-in socket support right now but the benefits of non-blocking IO in node are obviously huge. (It will. I just want to make sure I do integrated socket support right. I don't want to chase realtime frameworks because that's not Nodal's value prop, but I do want it to be easy to create socket connections when they're needed.)
- irregularexp 11y agoElixir + Phoenix seems like a better choice if websockets is going to be a core feature, since the BEAM's concurrency model is better and Phoenix's "Channels" abstraction is so solid. I wouldn't think of using Rails for that use case, even with ActionCable in tow, unless it was a minor feature.
- dev360 11y agoYES!!! I've been looking very carefully at this, but Elixir still feels intimidating to me. A friend of me gave me an ebook which I'm working through at the moment. For me, the jury is still out on whether I will be able to model my domain well in a language like Elixir.. I love Haskell, but I sometimes wonder if its a healthy attitude to be so stubbornly against OO. That said, I understand the arguments against essentially `this` and mutability. Any pointers on how to model your domain model in FP would be really welcome!