4 ms·

The problem is, the sort of devs who would jump right into Ruby On Rails a decade ago are now doing stuff with React, Node, Go, and (if they're lucky duckies) E

The problem is, the sort of devs who would jump right into Ruby On Rails a decade ago are now doing stuff with React, Node, Go, and (if they're lucky duckies) Elixir.

thedoops 8y ago
Elixir is an absolute pleasure. The benefits of Ruby's developer experience with a maintainable, scalable backbone.
- busterarm 8y ago
  You should have seen PragDave's Empex talk last month about what sucks about Elixir. It actually makes me look forward to the changes he proposed.
- cutler 8y ago
  Elixir adoption is going nowhere. If you search Indeed.co.uk by job title there are currently 7 Elixir jobs in London compared with 104 Ruby and 364 Python.
pmontra 8y ago
We had a split into frontend and backend lately. The front end was only a little JavaScript on static HTML pages when RoR was trending (btw, does anybody remember Prototype.js?) Still, it's easier to code a backend in Rails than in Phoenix (done that) or Django (inherited one). Both have extra layers that Rails proved to be unnecessary until the business scales to levels that very few companies reach. And if it doesn't, any MVP in any language can keep running fine for years. We can start debating about tradeoffs and premature optimizations but I don't remember any unicorn to shut down because it started with Rails (or PHP, hi Facebook!) and couldn't cope with the load. It's so much more about marketing and execution than technology.
spamizbad 8y ago
Kind of shocked this is getting downvoted. Look, this isn't about X being better than Y, it's simply the fact that there are now a litany of other technologies to grab people's interest. In the aughts, I watched Rails' meteoric rise: it was revolutionary and had few equals. Rails shifted the conversation away from baroque, enterprise-y frameworks towards tools that provided real developer productivity.

4 ms·

The problem is, the sort of devs who would jump right into Ruby On Rails a decade ago are now doing stuff with React, Node, Go, and (if they're lucky duckies) E

by spamizbad 8y ago

The problem is, the sort of devs who would jump right into Ruby On Rails a decade ago are now doing stuff with React, Node, Go, and (if they're lucky duckies) Elixir.

thedoops 8y ago
Elixir is an absolute pleasure. The benefits of Ruby's developer experience with a maintainable, scalable backbone.
- busterarm 8y ago
  You should have seen PragDave's Empex talk last month about what sucks about Elixir. It actually makes me look forward to the changes he proposed.
- cutler 8y ago
  Elixir adoption is going nowhere. If you search Indeed.co.uk by job title there are currently 7 Elixir jobs in London compared with 104 Ruby and 364 Python.
pmontra 8y ago
We had a split into frontend and backend lately. The front end was only a little JavaScript on static HTML pages when RoR was trending (btw, does anybody remember Prototype.js?) Still, it's easier to code a backend in Rails than in Phoenix (done that) or Django (inherited one). Both have extra layers that Rails proved to be unnecessary until the business scales to levels that very few companies reach. And if it doesn't, any MVP in any language can keep running fine for years. We can start debating about tradeoffs and premature optimizations but I don't remember any unicorn to shut down because it started with Rails (or PHP, hi Facebook!) and couldn't cope with the load. It's so much more about marketing and execution than technology.
spamizbad 8y ago
Kind of shocked this is getting downvoted. Look, this isn't about X being better than Y, it's simply the fact that there are now a litany of other technologies to grab people's interest. In the aughts, I watched Rails' meteoric rise: it was revolutionary and had few equals. Rails shifted the conversation away from baroque, enterprise-y frameworks towards tools that provided real developer productivity.