4 ms·
Honest question. What technology are people enjoying on the server-side with sites built in React or Angular? I've seen some of these done with Rails, and some
by zippergz 10y ago
Honest question. What technology are people enjoying on the server-side with sites built in React or Angular? I've seen some of these done with Rails, and some done with Node, neither of which I personally enjoy a whole lot. (Note, I'm not making an argument that either are BAD - just that I don't really like working with them). I'm curious to hear what other people are having success with in production.
- disease 10y agoScala and c#. Great tooling, static typing, functional and OO paradigms covered, fast (Scala runs fast once complied), flexible with tons of existing code already out there to be used or learned from.
- emodendroket 10y agoI have no complaints about C# and Webapi. Well, "no complaints" isn't exactly right but I like it.
- spinlock 10y agoPheonix looks promising. It's basically Erlang on Rails.
- bobwaycott 10y agoOr Rails on Erlang (even though I see what you did there).
- crdoconnor 10y agoDjango has always been relatively pleasant for me to develop in. Flask has been okay too. I almost learned Rails in 2007 when it was at the peak of its hype cycle but after reading a series of (not very well publicized) tirades about pain that Rails' magic caused I learned Django instead. I think node is at the peak of its hype cycle right now.
- sotojuan 10y agoElixir's Phoenix: https://dockyard.com/blog/2015/11/18/phoenix-is-not-rails https://dockyard.com/blog/2015/11/18/phoenix-is-not-rails
- spriggan3 10y agonot production ready but will be soon : asp.net core. If you want something like Rails with a statically typed language like C#, that's you best bet.
- gedy 10y agoNode.js, it's a great fit because it doesn't try to be much more than a thin framework for web services. The value of code JS sharing between server and client is a bit overblown imho, but sharing same language skills is nice.