- Support for transactions
- Predictable data binding for raw SQL queries (and just a more verbose DSL for the ORM in general - recently used Laravel and I was in awe of how much better it was -- I mean I can't even ask a database how many cats with blue eyes Suzie has without loading the rows into memory)
- Better support for database migrations, and better support for individual databases (generally improved adapters for each database -- composite indexes, and proper data types are two examples here)
- Support for deep relational data fetching
- Support for a LINQ-like IQueryable style of queries (perhaps using promises) -- for those unfamiliar with using LINQ (and specifically do DB operations), LINQ allows you to write and operate on queries with deferred execution until such point that the data is made available. What this roughly translates to is writing code and having it be turned into SQL by the ORM and only querying the database once the entire query has been built.
- Better sockets integration
- Integrated cache
I think this should speak volumes about Sails' readiness for production. I don't mean to harp on Balderdashy, they've done great work - but there's so much more to do. Right now if I wanted to start a new project I'd have a hard time choosing Sails over Laravel. They may be different languages but for many use cases I've seen the same or better performance from Laravel on HHVM. I honestly don't know how anyone can say they're loving it in production while these problems have remained unsolved. Every time I need to do something in my Sails application that strays from the most basic of operations, I end up having to write raw SQL or write a module in order to use sockets in any meaningful way. Personally, I'll be sticking to smaller Node.js libraries for a while yet. Not because I think Sails is bad, but because it's simply not ready.
1. The site and the courses look great but, why can't I sign up without a Facebook or Twitter account? This one issue was enough for me to leave the site. I compartmentalize my web affairs for many reasons and keeping my online accounts separate is very important for me. I'm writing this to encourage you (and others) to reconsider this practice.
2. I can see the icon that says "Beginner," but that doesn't tell me much. In your FAQ, I would recommend expounding on this. Beginner is too ambiguous.
All your feedback will be welcome, thanks!
https://courses.platzi.com/frequently-asked-questions/#perma...
This isn't at all meant to discredit the Balderdashy team - I'm glad the project exists and they're doing good things. However, we've been told that their focus is on their clients and on paying enterprise customers - which is completely understandable - but that leaves groups like us in the large queue of Github issues without any solution or resolution. A lot of what seemed like "useful magic" (blueprints, responses, parameter handling, auto-loading of various components) has turned into unpredictable or broken "magic" as our codebase grows.
I hope that the team has some time to work through their backlog and revisit or replace some of the more lacking pieces. I'd love to see Sails grow into a mature and stable framework in the future.
Basically it's just Express well structured and organised with some fancy features and nice CLI.
L.E. If anyone is interested how to replace Waterline with Mongoose into a Sails project, let me know. I did that a project.
http://nathanleclaire.com/blog/2013/12/28/the-good-the-bad-a...
It's a "good, bad, ugly" article, but it's old. Care to comment on any of the issues mentioned in the "bad and ugly" parts. Specifically, I wonder about the (alleged, possibly old) lack of Waterline ORM support for associations / relational data. I'm hoping that's a softball question. I love seeing new approaches succeed!
Deep relational fetches would be very very helpfull though, now you basically have to cobble up seperate async fetches to do more complex joins.
Seconded. I'm still early on with a project where we're very close to replacing Waterline for this reason. I always thought ActiveRecord was one of the great strengths of Rails but unfortunately I'm finding Waterline to be the biggest weakness of Sails.
And then, we hope to do a full course on either React.js and JS app dev or Social Media Marketing and Community Management. Still debating that. What do you guys think?
