6 ms·
Betting on the wrong horse
- bluejekyll 11y agoDisturbingly, I could have written this exact article. But I never made the "ruby" mistake, to some of us, that was obvious, though Rails was a cool concept, just better implemented in other more performant languages.
- jacquesm 11y ago> Rails was a cool concept, just better implemented in other more performant languages. Can you list your preferences?
- reitanqild 11y agoPHP - Rails inspired some great frameworks on PHP and once they became available I promptly switched. I realize I might take some flak for this : )
- jacquesm 11y agoSpecifically which framework? (And anybody giving you flak for using PHP is telling more about themselves than about you.)
- rorykoehler 11y agoProbably talking about Laravel.... I'm curious what you think not liking PHP says about someone?
- tzs 11y agoHe didn't say that someone not liking PHP says something about them. What he said was that someone giving flak to another for using PHP says something about them.
- rorykoehler 11y agoAh ok sorry. I misread that.
- reitanqild 11y agoUsed to be Symfony. Now I am a happy Java camper but not on a Rails like framework ATM at least.
- bluejekyll 11y agoFor Java I would say that Dropwizard if not a direct copy, definitely was inspired by the simplicity of Rails. For Python it would probably be Django, but I'm still a novice in Python. In terms of build chain, the declaritive nature of Maven as a build tool (far from perfect, but extensible) and then likewise in Python the setup.py bits. Looking at other languages, Cargo has a similar declarative build chain for Rust, and I think a lot of the package management that we see out there was inspired generally by Ruby. Again, cool concepts, but for me Ruby never was more than a toy.
- fennecfoxen 11y ago> Rails was a cool concept, just better implemented in other more performant languages. Agree and disagree. The first win of Rails-inspired systems is the idea of actually providing decent building blocks for building a large application instead of just throwing you a router and some HTTP tools like the Sinatra-a-likes do. (If I had a dollar for ever minute I wasted dealing with writing something any decent Rails clone would have given me for just-about-free... that'd describe about 25% of several jobs I've held. :P) But the two biggest wins of running Rails specifically are having a major community's worth of software around it, and having a Very Expressive Language with which to build the rest of it. These let you save on developer time in a variety of important circumstances where dealing with complexity is much more important than dealing with performance (internal-facing applications, for one, or XYZ-management-systems).
- awjr 11y agoI can remember being at my first contract position in 1995/6 and suggesting to people that this new language Java was kinda cool and being told by many other people I was working with that it wasn't worth pursuing. So I didn't... JavaScript is really cool and I did pursue that one. :)
- deleted 11y ago[deleted]
- wtbob 11y agoThe article displays nothing but a blank page with JavaScript turned off…
- groundCode 11y agoWell, the blog's author is a Javascript developer :)
- wincent 11y agoGuilty as charged. The blog is new (days old), but server rendering will be coming.