Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why Meteor will kill Ruby on Rails

differential.io

Post reply on HN
Print view View original

211–220 of 336 posts

Re: Why Meteor will kill Ruby on Rails

#211

Post by joshowens »

awj wrote: post #111
programminggeek wrote: post #72

Earlier quoted context omitted.

I agree, but when Rails came out, there was a whole lot of Ruby on Rails is going to kill Java type posts. I guess this means Meteor is reaching some mindshare.

Yeah, and we saw how well that worked. Java projects sprung up to incorporate the good ideas from Rails, Rails itself picked up a load of developers and evolved into something decent, and the world moved on. Nothing was killed, but all the boats rose. I'm thinking maybe the drama wasn't a requirement for this to happen. Perhaps Meteor devs could experiment with that idea.

Without the drama, this post with a different title would have fallen off the front page in about 15 minutes.

Re: Why Meteor will kill Ruby on Rails

#212

Post by nostrademons »

joshowens wrote: post #206
neya wrote: post #166

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 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…

I'd be willing to go toe to toe on building a clone in Meteor while you build it in rails.

That actually might be a neat one-day hackathon: strip a popular website down to its essence and implement it as fast as you can with your favorite framework of choice.

I'd be willing to go toe-to-toe with you guys on no framework at all - just HTML/CSS/JS and perhaps a little JSON feed to an AppEngine datastore if data needs to be persisted and shared among multiple users.

Re: Why Meteor will kill Ruby on Rails

#213

Post by joshowens »

ambiate wrote: post #75
acqq wrote: post #20

I 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.

http://docs.meteor.com/#spiderable Could this could be used if the browser does not support JS?

Yes, and you can control a list of user agents that it activates for.

Re: Why Meteor will kill Ruby on Rails

#214

Post by vysakh0 »

neya wrote: post #166

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 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…

Totally agree with you. When you said about the Facebook clone part, I had to nod my head even more faster :) coz I once built one, blogging it side by side http://vysakh.quora.com/Making-a-Facebook-clone-using-Rails-...

Re: Why Meteor will kill Ruby on Rails

#215

Post by bigiain »

joshowens wrote: post #142
jarsbe wrote: post #119

Earlier 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.

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

#217

Post by kayoone »

hippee-lee wrote: post #185
joshowens wrote: post #142

Earlier quoted context omitted.

Sure: http://www.shinglecentral.com/ http://assistant.io/ http://lister.io/ Are just a few from the last 1.5 months.

Can you point to some example that are a bit more complex in nature? My issue (that I identified with the backbone tutorials and re affirmed with the Angular tutorials) is that simple apps are easy to do with x, y or z. But if the new one or that one is going to replace the old one there should be 37 signals level complexity type apps out there. While I can't speak for Meteor, I don't see anything running on angular…

podio.com is a pretty large enterprise app based on a Rails+Backbone stack. Their approach is to have multiple Backbone Apps (dashboard, contacts, tasks, calendar) for different modules. So if you switch modules you have page refresh and from there its a Backbone App...i like that approach and their app is pretty awesome.

Re: Why Meteor will kill Ruby on Rails

#218

Post by arocks »

rafekett wrote: post #190
qiqing wrote: post #130

Earlier quoted context omitted.

Z-mongo-admin, the Meteor equivalent of phpMyAdmin, was a project that won a prize at the Meteor hackathon earlier this year. [1] Here's one of its authors, Geoffrey Vedernikoff, speaking at HackMIT. [2] Perhaps you could compare notes with the team to see what's going wrong in your version. [1] http://www.meteor.com/blog/2013/07/09/congratulations-to-the... [2] http://www.meteor.com/blog/2013/10/11/meteor-at-hackmit…

I'm sure his project worked, too, it just didn't scale.

This is true. In the Q&A of this video [1], the creator of Z Mongo Admin mentions that the browser will hang if the collections are huge.

[1]: https://www.youtube.com/watch?v=yeF_b8EQcK0

Re: Why Meteor will kill Ruby on Rails

#219

Post by salimane »

nostrademons wrote: post #207
derefr wrote: post #89

Earlier quoted context omitted.

Making repeated prototypes (in est, experiments ), quickly, is how you approach entrepreneurialism in any sort of scientific manner. Nothing needs to scale, or work at the edge-cases, until it has product-market fit; and you might need to write twelve or twenty or two-hundred different apps until you find one that works out that way. That's what makes these frameworks popular with HN: startup founders are not in the…

That's all true, but I'm also beginning to wonder how much you actually need those frameworks to build MVPs quickly. I used to do the bulk of my prototyping with Python + Django + JQuery + Postgres or AppEngine Datastore. Of late, I've switched a lot of it to just straight HTML + Javascript + a JSON feed from backends. If I need server-side computation, I'll build a quick Go or webapp2 app on AppEngine. I work just a…

is there any small library ala "notjquery.js" that is a drop in replacement for jquery but that calls the browser native stuff directly ? serious question ?

Re: Why Meteor will kill Ruby on Rails

#220

Post by Tarang »

I use Meteor alot.

Some of the issues mentioned here were about a lack of scalability in terms of larger sized apps and to the number of simultaneous users it can handle.

If you have a large app you can use subscriptions that change as you view them. You can indeed have large 100,000 item collections without any hiccups or slowness. The issues people display here are if you have this 100k database downloaded on your browser which is unrealistic.

The second as to scalability user-wise. It is possible to scale meteor by altering some code. Meteor's still a baby but their 1.0 release will definitely sort this out:

The issues relate to how publish functions are handled & how mongodb interacts with meteor. These will be heavily optimized by running publish functions less & using a mongodb replica set emulated via meteor or through mongodb's oplog.

I have built before with .NET (I hate it the most), Java, Rails, PHP, Coldfusion, you name it! One thing Meteor helps me do is build fast and expect something that works without bugs at the end. Its nice to experiment around with what people like till we get it right.

I'm going to go so bold as to say Meteor will let people experiment with many ideas just as VCs do with ideas but here you can get that one which works without much cost & time to develop it.

RoR is nice but when it comes to a funky front-end user experience its not nice. The backend is loads of fun!

Post reply on HN