DEV Community

Discussion on: My search for supremacy

Collapse
 
stefandorresteijn profile image
Stefan Dorresteijn

Thanks! Yes, I think building a central API and building distributed frontend applications is an innovation we really needed. Almost every website I build now has a JavaScript frontend using a framework like React or Vue (and recently I've added GraphQL as well.)

The problem still lies with the choice between Rails and NodeJS for me in most projects and lately it's come down to the special functionality I need (real-time, async, etc.), I would just prefer a language that does all of that. Elixir comes close but is still very functional.

Collapse
 
andy profile image
Andy Zhao (he/him)

Appreciate the quick response! I've heard really good things about Elixir from a few people, but still don't know much about it.

Also, thanks for the clarification about your choice. That makes a whole lot more sense now. Since you mentioned it, I think Rails is headed toward more async and real-time features now with Rails 5, ActionCable, and just more JavaScript support. Do you think it'll "catch up" to a point where those features would match NodeJS?

Thread Thread
 
stefandorresteijn profile image
Stefan Dorresteijn

Yeah, I'm trying to learn Elixir during my free time but haven't gotten around to using it in a real project yet.

Yeah, Rails will improve but NodeJS is non-blocking in its very core so it's very much built for async functionality. I'm not sure Rails will ever catch up to NodeJS, especially with how many people are moving towards NodeJS (and away from Rails) lately but we'll see. I don't think the OOP crowd has the majority right now in web development either so we're really up against it.