4 ms·

> [citation needed] Okay. The year is 2005. PHP5 was fresh out of the oven and most people were still on PHP4. From PHP's point of view, there's rumors of some

by niftich 10y ago

> [citation needed] Okay. The year is 2005. PHP5 was fresh out of the oven and most people were still on PHP4. From PHP's point of view, there's rumors of something happening in the Ruby community that will be big, and should be talked about [1]. Then Rails 1.0 drops at the end of the year. From this Slashdot thread [2] on the announcement you can gauge the contemporary reaction; comments detail the fact that Rails was breath of fresh air from the configuration-heavy Java frameworks of the day -- represented by Struts [3], but others weren't much different in this regard, as these books from 2002 and 2004 about alternatives to Struts show [4][5]. Several ASP developers, detail their positive experiences in switching their web development to Rails [6][7][8]. The PHP world is forever changed -- by 2006, frameworks inspired by Rails abound [9]. "Ruby on Rails" becomes a popular phrase, some frameworks borrow the naming scheme along with the ideas: "Groovy on Grails" [10] tries to bring Rails' ideas to the Java world, "PHP on Trax" (formerly "PHP on Rails" [9]), "ColdFusion on Wheels" [11]. I'd say Rails made quite the splash. [1] https://blog.phpdeveloper.org/2005/12/31/25/ https://blog.phpdeveloper.org/2005/12/31/25/ [2] https://developers.slashdot.org/story/05/12/14/0034219/ruby-on-rails-10-released https://developers.slashdot.org/story/05/12/14/0034219/ruby-... [3] http://weblog.rubyonrails.org/2005/2/22/comparing-struts-to-action-pack-railties/ http://weblog.rubyonrails.org/2005/2/22/comparing-struts-to-... [4] https://www.safaribooksonline.com/library/view/programming-jakarta-struts/0596003285/ch01s08.html https://www.safaribooksonline.com/library/view/programming-j... [5] https://www.safaribooksonline.com/library/view/programming-jakarta-struts/0596006519/ch01s07.html https://www.safaribooksonline.com/library/view/programming-j... [6] http://weblog.rubyonrails.org/2005/6/28/asp-net-vs-rails-analysis-from-a-veteran/ http://weblog.rubyonrails.org/2005/6/28/asp-net-vs-rails-ana... [7] http://weblog.rubyonrails.org/2005/12/20/neters-tell-scoble-why-they-left-for-rails/ http://weblog.rubyonrails.org/2005/12/20/neters-tell-scoble-... [8] http://weblog.rubyonrails.org/2005/7/5/not-knowing-where-it-hurts-in-asp-net/ http://weblog.rubyonrails.org/2005/7/5/not-knowing-where-it-... [9] https://h3rald.com/articles/rails-inspired-php-frameworks/ https://h3rald.com/articles/rails-inspired-php-frameworks/ [10] http://grails.1312388.n4.nabble.com/Groovy-on-Rails-is-no-more-kind-of-td1313422.html http://grails.1312388.n4.nabble.com/Groovy-on-Rails-is-no-mo... [11] http://cfwheels.org/blog/how-oo-almost-destroyed-business/ http://cfwheels.org/blog/how-oo-almost-destroyed-business/

vorg 10y ago
> Groovy on Grails The source you quote says "Groovy on Rails", which was the official name until it was contracted to "Grails" due to the insistence of the Rails crowd that "on Rails" not be used in any other product names. The "Groovy on Grails" phrase you wrote was a later unofficial but intended mispronunciation of the earlier name put out by the Grails crowd to make it sound like "Ruby on Rails" as a snipe at the Rails crowd. To those of us who thought Groovy would make a good language outside of its use in Grails, the mispronunciation made it sound like someone in the Grails crowd thought Groovy's only use was for scripting Grails.
inimino 10y ago
I think we disagree on two points. First, I don't think the influence of RoR was as sweeping as you do. This is probably just a difference in perspective or preference. Second, regardless of that, I think the JS ecosystem is well-enough explored that the chances that some single new idea or platform is going to dramatically change everything doesn't seem very likely to me. For reasons I've mentioned in my top-level comment on this page, I think diversity of the JS ecosystem is going to be with us for a while.

by niftich 10y ago

vorg 10y ago

> Groovy on Grails The source you quote says "Groovy on Rails", which was the official name until it was contracted to "Grails" due to the insistence of the Rails crowd that "on Rails" not be used in any other product names. The "Groovy on Grails" phrase you wrote was a later unofficial but intended mispronunciation of the earlier name put out by the Grails crowd to make it sound like "Ruby on Rails" as a snipe at the Rails crowd. To those of us who thought Groovy would make a good language outside of its use in Grails, the mispronunciation made it sound like someone in the Grails crowd thought Groovy's only use was for scripting Grails.

inimino 10y ago

I think we disagree on two points. First, I don't think the influence of RoR was as sweeping as you do. This is probably just a difference in perspective or preference. Second, regardless of that, I think the JS ecosystem is well-enough explored that the chances that some single new idea or platform is going to dramatically change everything doesn't seem very likely to me. For reasons I've mentioned in my top-level comment on this page, I think diversity of the JS ecosystem is going to be with us for a while.