Betting on the wrong horse
wincent.com
Betting on the wrong horse
1–10 of 16 posts
Re: Betting on the wrong horse
#2Disturbingly, 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.
Re: Betting on the wrong horse
#3Disturbingly, 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.
> Rails was a cool concept, just better implemented in other more performant languages.
Can you list your preferences?
Re: Betting on the wrong horse
#4Disturbingly, 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.
> Rails was a cool concept, just better implemented in other more performant languages. Can you list your preferences?
PHP - Rails inspired some great frameworks on PHP and once they became available I promptly switched.
I realize I might take some flak for this : )
Re: Betting on the wrong horse
#5I 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. :)
Re: Betting on the wrong horse
#6Earlier quoted context omitted.
> Rails was a cool concept, just better implemented in other more performant languages. Can you list your preferences?
PHP - Rails inspired some great frameworks on PHP and once they became available I promptly switched. I realize I might take some flak for this : )
Specifically which framework? (And anybody giving you flak for using PHP is telling more about themselves than about you.)
Re: Betting on the wrong horse
#7Earlier quoted context omitted.
PHP - Rails inspired some great frameworks on PHP and once they became available I promptly switched. I realize I might take some flak for this : )
Specifically which framework? (And anybody giving you flak for using PHP is telling more about themselves than about you.)
Probably talking about Laravel.... I'm curious what you think not liking PHP says about someone?
Re: Betting on the wrong horse
#8Earlier quoted context omitted.
Specifically which framework? (And anybody giving you flak for using PHP is telling more about themselves than about you.)
Probably talking about Laravel.... I'm curious what you think not liking PHP says about someone?
He 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.
Re: Betting on the wrong horse
#9Earlier quoted context omitted.
Specifically which framework? (And anybody giving you flak for using PHP is telling more about themselves than about you.)
Probably talking about Laravel.... I'm curious what you think not liking PHP says about someone?
Used to be Symfony. Now I am a happy Java camper but not on a Rails like framework ATM at least.
Re: Betting on the wrong horse
#10Disturbingly, 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.
> 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).