2 ms·
"i don't think the author was coming at this from a techie's perspective, but from the perspective of a manager/leader who has to make a technology choice." Ye
by chaostheory 19y ago
"i don't think the author was coming at this from a techie's perspective, but from the perspective of a manager/leader who has to make a technology choice."
Yes a non-technical manager in a large corporation... that makes perfect sense to post this on ycombinator...
"given the framework, Its hard to separte Rails "the technology" from Rails "the movement" "
Umm only if you're not technical or too lazy to really study it (making half assed assumptions instead)... I really don't mind good critiques of rails (slow, lacking standard functionality, ...), but come on - this has got to be one of the most stupid article posted
" the key difference between a knucklehead java programmer and a knucklehead Ruby/Rails programmer is that the former can be found out much more readily (more peeps are familiar with java) than the latter."
(being a former java programmer) no offense but can you actually back this up with real numbers/case studies instead of pulling it out of your ass - like the author did?
- sloba 19y agochaos, you make good points re: separation of technology/movement and immaturity/inexperience/posing of Rails developers .. i can't site a case study, but having to re-write a few supposedly "Rails" apps myself, i can tell you - at least anecdotally -- that there is some truth to the poser Rubyist observation ..