> 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.
I choose to use javascript, nobody chooses to have cancer.
Why Meteor will kill Ruby on Rails
261–270 of 336 posts
Re: Why Meteor will kill Ruby on Rails
#262Earlier quoted context omitted.
I'd love to see some examples of these apps, are you able to please share?
Sure: http://www.shinglecentral.com/ http://assistant.io/ http://lister.io/ Are just a few from the last 1.5 months.
Re: Why Meteor will kill Ruby on Rails
#263Earlier quoted context omitted.
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
This is a discussion about a javascript framework. Meteor relys on javascript on the client and the server so how should it work with noscript? 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
#264Earlier 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
Re: Why Meteor will kill Ruby on Rails
#265Earlier quoted context omitted.
> 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…
What is MEAN? It's particularly hard to Google, even with additional keywords.
[1] http://blog.mongodb.org/post/49262866911/the-mean-stack-mong...
Re: Why Meteor will kill Ruby on Rails
#266Earlier quoted context omitted.
Sure: http://www.shinglecentral.com/ http://assistant.io/ http://lister.io/ Are just a few from the last 1.5 months.
cough in the UK shingles is the name of a very uncomfortable medical condition... :D
Re: Why Meteor will kill Ruby on Rails
#267Earlier quoted context omitted.
> 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…
What is MEAN? It's particularly hard to Google, even with additional keywords.
Re: Why Meteor will kill Ruby on Rails
#268It concerns me that the selling points of Meteor are the same as the old selling points of ASP.Net. - Both seek to make the divide between server and client "seamless", marshaling data back and forth so that you can "call" server code from the client and vice-versa. - Both tout the ability to do all your development in a single language - Both claim impressive gains for RAD ASP.Net had some impressive demos for its t…
But I have to admit that it is pretty funny that comparing a framework to ASP.NET is apparently the nerd equivalent of insulting someone's mother.
Re: Why Meteor will kill Ruby on Rails
#269Earlier 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…
> . You just have to do so much glueing
In your previous post. Then you list out MEAN(Mongo, Express, Angular, Node), which is all glueing. I have used this stack extensively, and I must say its not even close to Rails. In fact it's not even on the same planet.
After all you guys finish your piddly todo lists, start trying to write some real business logic in Node, and see how far it gets you. There is a reason the Meteor team chose fibers. You can async.waterfall all you want but structuring your code in a synchronous manner, lets you get stuff done.
People tout Node and Meteor for real time stuff. I could do similar things with SSE and Rails/Ember or Angular. The users of your applications don't care if you use Websockets and really most of the time you don't even need Websockets, you just need SSE or long polling.
Re: Why Meteor will kill Ruby on Rails
#270Earlier quoted context omitted.
> 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…
What is MEAN? It's particularly hard to Google, even with additional keywords.