Re:Is Rails still relevant in 2018?
by WillPostForFood on Tuesday August 28, 2018 @10:18AM
(#17858927)
Speed of development, or runtime speed? Language won’t matter for runtime speed except in the .1% of high load apps. In my experience speed of development will vary quite a bit based on language and quality of frameworks. I went from C# shop to Ruby/Rails and the pace increased substantially, though cultural differences are intertwined with language choices.
Re:Is Rails still relevant in 2018?
by ryanbrunner on Tuesday August 28, 2018 @12:43PM
(#17860343)
Runtime speed, as an example of one of the few considerations when choosing a language that isn't related to code quality and maintainability.
I agree though that it's not relevant for nearly all web applications (and even for those where it is, it doesn't require that everything is done in a performant language)
Re:Is Rails still relevant in 2018?
by chiefalchemist on Tuesday August 28, 2018 @11:05AM
(#17859332)
> The two are equivalent in most cases.
Yes and no. The most elegant technology solution in the world does mean squat if it doesn't solve the problem the client / user needs solved.
Technology and solution are not the same thing.
Re:Is Rails still relevant in 2018?
by ryanbrunner on Tuesday August 28, 2018 @12:44PM
(#17860355)
Sure, but the choice of language is rarely a factor in this, barring very specialized subdomains where library support is limited to a few languages. There's very few web applications that couldn't have been written in virtually any modern language.
I think ideally they are the same, but doing a re-write isn't cost free - opportunity cost as you're not doing feature customers care about, new bugs being created, old bugs re-appearing etc etc.
Pretty much speed is the only concern for the vast majority of web applications, it isn't really that big a concern for most web applications, and even then it's less about choosing the fastest language and more about limiting yourself to a still pretty broad set of "faster" languages.