2 ms·

I've used sails 3 years ago on a startup that we wrote from scratch. Don't want to be negative but it is by far the worst framework and ORM I've ever used. Str

I've used sails 3 years ago on a startup that we wrote from scratch. Don't want to be negative but it is by far the worst framework and ORM I've ever used. Strongly recommend reading this[0] before you even start fiddling with the framework. Even tho there are 100 wrong things about it the absolute worst: ORM "migrations" work in a way that they drop the tables and and then re-create them. If you have a lot of data the table is dropped and you get Out Of Memory exception - what a great ORM! [0] https://kev.inburke.com/kevin/dont-use-sails-or-waterline/ https://kev.inburke.com/kevin/dont-use-sails-or-waterline/

mikermcneil 9y ago
Creator of Sails here. I’d like to set the record straight: The automigrations system is not, and was never, designed for production use. Sails/Waterline documentation explicitly and repeatedly warns against using this feature in production. On top of that, developers are forced to accept a prompt on the terminal the first time they lift an empty new app indicating that they understand this. The only way to make the prompt go away permanently is to hard-code configuration, indicating that you understand what automigrations are designed to do. In fact, just to be safe and prevent accidents, automigrations are forcefully disabled in production mode. In other words, to get your production/staging app into a state where this criticism is relevant, you have to ignore console warnings, skip reading the documentation, and go out of your way to trick the framework into thinking you’re running your app in development mode. I won’t beat a dead horse re other points in that 3-year-old blog post, except to say that, 3 years ago, some of them had merit. Those have been addressed in the Sails 1.0 release.
- jambaday 9y ago
  So, is there any production-ready migrations system ?
  - mikermcneil 9y ago
    Of course— luckily there are many great, framework-agnostic options for use in post-production. I usually use knex.

mikermcneil 9y ago

Creator of Sails here. I’d like to set the record straight: The automigrations system is not, and was never, designed for production use. Sails/Waterline documentation explicitly and repeatedly warns against using this feature in production. On top of that, developers are forced to accept a prompt on the terminal the first time they lift an empty new app indicating that they understand this. The only way to make the prompt go away permanently is to hard-code configuration, indicating that you understand what automigrations are designed to do. In fact, just to be safe and prevent accidents, automigrations are forcefully disabled in production mode. In other words, to get your production/staging app into a state where this criticism is relevant, you have to ignore console warnings, skip reading the documentation, and go out of your way to trick the framework into thinking you’re running your app in development mode. I won’t beat a dead horse re other points in that 3-year-old blog post, except to say that, 3 years ago, some of them had merit. Those have been addressed in the Sails 1.0 release.

jambaday 9y ago
So, is there any production-ready migrations system ?
- mikermcneil 9y ago
  Of course— luckily there are many great, framework-agnostic options for use in post-production. I usually use knex.