4 ms·
Rails was never really a major leap forward in anything, more so an evolution with convention-over-configuration and a strong community presence that establishe
by Dirlewanger 8y ago
Rails was never really a major leap forward in anything, more so an evolution with convention-over-configuration and a strong community presence that established best practices early. It also hasn't been "cool" for years, it's an entrenched player that "just works". One could argue with all the Rubyists going to Elixir that's part of the cycle, but for many people that's been a net positive.
And then there's those altogether dropping Elixir for Go...
- jules 8y agoRails was a major leap forward because the competition was really bad: PHP and Java Struts.
- wuliwong 8y agoI think that Rails using Ruby was a big deal. It was definitely different. Not sure if it was forward, backwards or lateral but it certainly was a big change beyond just "convention of configuration."
- cpursley 8y agoI doubt you'll find many people dropping Elixir for Go... And Ruby was a major leap forward ~ in productivity.
- dnautics 8y agoIf we believe the cycle model, then the people dropping elixir for go will come back when they're tired of dealing with kubernetes and when they realize that being a dynamic language isn't all that terrible (if done correctly).
- sanderjd 8y agoYeah, I think this is actually calling out a major weakness in the original comment's hype cycle model. Sometimes step #5 ("Five years pass...") doesn't happen in that way. Sometimes what happens is that the new technology has been found to be generally useful, though imperfect, as everything is. People may be evolving it in different directions, perhaps incorporating elements of the old technology the new one replaced, but it isn't being fundamentally abandoned. The tough part is that you don't know which version of step #5 will happen when you're surveying the world at step #4. If it was easy to figure this stuff out, they wouldn't pay us to try :)