14 ms·
I had my doubts but read the post to see where I could be enlightened. Two points sums it up for me: 1. Phoenix+Elixir [a modern Rails successor] 2. [satis
by karmakaze 8y ago
I had my doubts but read the post to see where I could be enlightened. Two points sums it up for me:
1. Phoenix+Elixir [a modern Rails successor]
2. [satisfy] both corporates and startups
I don't know who needs point 2. Perhaps consulting or a dev who only wants to learn a single stack? Not me.
I've used Rails at a scale where it hurts. Phoenix+Elixir is great if a little learning curve is okay. Spring+Java is bloated for many use cases so I have found and used microframeworks such as Javalin+Kotlin+JDBI which is far superior to Node on the back-end. For even smaller projects Go is a fine choice if you don't mind the simplicity which is simultaneously it's strong and weak point.
- mercer 8y agoI completely agree. I'd stick with Rails or opt for Elixir, Clojure, or maybe Go instead. I'm balls-deep in the Node.js ecosystem and the only reason I would choose it over Rails or the others is because of React + TypeScript. React is by far my favorite 'templating language' and TypeScript makes JS pretty decent. Basically, if I can get away with it I'd go for Phoenix+Elixir, followed by Clojure/ClojureScript. If I can't, I'd go for Rails. If for whatever reason that isn't an option, C# or Java. Node inhabits this weird in-between world that doesn't offer quite enough of anything, and has some serious drawbacks.