Re:Why Meteor will kill Ruby on Rails
by joshowens on Wednesday October 30, 2013 @08:00PM
(#6644402)
Insecure is there to help speed development when you are getting started.
All frameworks can do their best to compensate for security holes, but ultimately people need to pay attention to it. That being said, Meteor offers a call method and code runs on the server - if security is a concern then you should pay attention to what happens on the server.
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.
This is a thing for Meteor already. For example, if you have the insecure package enabled, you can can make changes directly to the database from the browser console. However, this particular issue can easily be detected prior to deploying to production.