Why Meteor will kill Ruby on Rails
251–260 of 336 posts
Re: Why Meteor will kill Ruby on Rails
#252This is bullshit. In my whole experience as a full stack developer, after having tried various technologies and languages and frameworks - including ones built with PHP, Ruby, Scala, Javascript and Golang, I can this say with full confidence and can afford to put my name and credibility to stake - Nothing is going to replace Ruby on rails anytime soon. I wish something would, but nothing at the moment, is even close…
This is bullshit. In my whole experience as a full stack developer, after having tried various technologies and languages and frameworks - including ones built with Perl, PHP, ColdFusion, and WebObjects, I can this say with full confidence and can afford to put my name and credibility to stake - Nothing is going to replace Enterprise JavaBeans anytime soon. I wish something would, but nothing at the moment, is even c…
Re: Why Meteor will kill Ruby on Rails
#253Earlier quoted context omitted.
Sure: http://www.shinglecentral.com/ http://assistant.io/ http://lister.io/ Are just a few from the last 1.5 months.
I'm sure you aren't going to worry too much, but you know some of us only see this: https://dl.dropboxusercontent.com/u/7633426/shinglecentral.p... https://dl.dropboxusercontent.com/u/7633426/assistantio.png https://dl.dropboxusercontent.com/u/7633426/listerio.png
If you want to use a javascript tool you´ll have to add an exception for this tool.
Re: Why Meteor will kill Ruby on Rails
#254Earlier quoted context omitted.
Thank you for your peaceful tone (unlike the author's). But I think there are a lot of opinions mixed up with your facts: >The sad thing about Rails is it largely stagnated for some time >You just have to do so much glueing >These are solved problems on node And to be clear, Node is not a 100% perfect platform either. >I think the author is attempting to elude to the cargo-cult that hit Rails will migrate to Meteor.…
> And to be clear, Node is not a 100% perfect platform either. Absolutely. But as a software piece, I think it can apply itself to the web more easily than Ruby currently can. > Of all the options available, why Meteor? Right, there are plenty of options, MEAN is getting nicely popularized. You also have Derby. > Like someone on this thread said, it has a lot more evolving to do, to even become on par with rails in t…
Re: Why Meteor will kill Ruby on Rails
#255Re: Why Meteor will kill Ruby on Rails
#256I think you need to learn how to code better
Re: Why Meteor will kill Ruby on Rails
#257Re: Why Meteor will kill Ruby on Rails
#258> Let's be real, Javascript is the #1 language on Github and for good reason - it runs everywhere. Cancer is #1 disease in the world, but that doesn't mean I want it.
Re: Why Meteor will kill Ruby on Rails
#259Re: Why Meteor will kill Ruby on Rails
#260"When a client asks us to build an app, they are really asking for a fully interactive web app that utilizes javascript to get rich client interfaces." Or maybe they really are just asking you for an app, but you'd rather build a fully interactive web app that utilizes javascript to get rich client interfaces.
No, the client that spawned this blog post was specifically asked for heavy google maps integration. We haven't had one client asking for just a server side app in years. I've been doing this for 8-9 years, I have a good idea on how to talk with my clients :)
As an author with every post and submission you make a conscious decision about what is important to you. Do you want to enlighten your readers or do you want to gain notoriety at the expense of your audience?
Ask yourself, do you want to be the Daily Mail or Le Monde?