News for hackers. Stuff that matters.
Re:Why Meteor will kill Ruby on Rails by MichaelGG on Wednesday October 30, 2013 @09:49PM (#6644767)
I've not used Meteor. How exactly does "insecure" help speed development? Certainly any code you write with it is worthless, right? I mean, before production you need to remove it and rewrite it using another method, so what's the point? Or do you mean it's useful on the sysadmin side, as a REPL-like data access console?
Re:Why Meteor will kill Ruby on Rails by jaredsohn on Wednesday October 30, 2013 @09:57PM (#6644782)
From meteor.com:

>By default, a new Meteor app includes the autopublish and insecure packages, which together mimic the effect of each client having full read/write access to the server's database. These are useful prototyping tools, but typically not appropriate for production applications. When you're ready, just remove the packages.

Re:Why Meteor will kill Ruby on Rails by ajlin500 on Wednesday October 30, 2013 @10:05PM (#6644806)
It makes it easy to run DB calls from the chrome console to insert and modify test data