Is the inability to get HTML without being a javascript engine going to be a problem for major adoption? (I know there are hacks around using phantomjs to generate HTML for non-JS clients -- is that a viable solution for serious sites?)
Why Meteor will kill Ruby on Rails
11–20 of 336 posts
Re: Why Meteor will kill Ruby on Rails
#12It depends on your definition of kill.
If you mean for new project starts, it might severely diminish it, but I don't think it will flat out end its popularity any more than Rails killed Java.
Also, it depends on what type of project you are talking about. For something at large scale, my guess is meteor won't be any more successful than Rails has been at huge scale (like Twitter).
I do agree that using one language end to end might be an awesome developer experience, but I wish that language wasn't JavaScript. I won't go into great detail as to why, but I would not want to build a large JavaScript app. That sounds incredibly painful and unpleasant to me.
Re: Why Meteor will kill Ruby on Rails
#13> Java promised this too us back in the 90's, but it was too big and bloated and hard to work with
LOL @ Java being described as "hard to work with" in comparison to JavaScript. Major indicator of JS developer Stockholm Syndrome right there.
Re: Why Meteor will kill Ruby on Rails
#14Is the inability to get HTML without being a javascript engine going to be a problem for major adoption? (I know there are hacks around using phantomjs to generate HTML for non-JS clients -- is that a viable solution for serious sites?)
Meteor has a package 'spiderable' which allows Google to index the content — we're having no problems with it.
Re: Why Meteor will kill Ruby on Rails
#15How exactly did the author come to this Meteor and Rails dichotomy? What do they have alike besides being web application frameworks, of which there are endless?
This makes about as much sense to me as "Why Flask will kill Zend".
Re: Why Meteor will kill Ruby on Rails
#16Technically, you can use meteor with rails https://github.com/tmeasday/ruby-ddp-client, so I don't know if meteor is killing rails anytime soon.
Re: Why Meteor will kill Ruby on Rails
#17If you don't accept its cookies, it shows you a blank page.
I hate to be negative but that's not how to win my confidence.
Re: Why Meteor will kill Ruby on Rails
#18"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.
Re: Why Meteor will kill Ruby on Rails
#19Is the inability to get HTML without being a javascript engine going to be a problem for major adoption? (I know there are hacks around using phantomjs to generate HTML for non-JS clients -- is that a viable solution for serious sites?)
Meteor has a package 'spiderable' which allows Google to index the content — we're having no problems with it.
Yes, that's the PhantomJS hack.
Re: Why Meteor will kill Ruby on Rails
#20I can't read the site (there's nothing in HTML) but is this a framework that doesn't produce pages viewable without JavaScript? If it is against HTML, my vote is against it.