The join button is completely broken in Chrome beta.
Live Sails.js Course
31–40 of 48 posts
Re: Live Sails.js Course
#32My Sails.js wishlist:
- 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.
Re: Live Sails.js Course
#33My Sails.js wishlist: - 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 (gen…
Sails is very modular, if you wanted to replace the ORM with something else you could just replace the Waterline hook. Waterline is still pretty young and all of these features would be great to get added! We are always looking to add new contributors if anyone would like to help move some of these features along.
Re: Live Sails.js Course
#34My Sails.js wishlist: - 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 (gen…
Sails is very modular, if you wanted to replace the ORM with something else you could just replace the Waterline hook. Waterline is still pretty young and all of these features would be great to get added! We are always looking to add new contributors if anyone would like to help move some of these features along.
Thanks Cody, I appreciate the reply.
Re: Live Sails.js Course
#35Earlier quoted context omitted.
Sails is very modular, if you wanted to replace the ORM with something else you could just replace the Waterline hook. Waterline is still pretty young and all of these features would be great to get added! We are always looking to add new contributors if anyone would like to help move some of these features along.
Thanks Cody, I appreciate the reply.
Yeah no problem. If you want to go into some more details about production issues my email is in my profile.
Re: Live Sails.js Course
#36The livestreaming of the class is over now. But we'll upload the recordings ASAP to:
https://courses.platzi.com/classes/develop-apps-sails-js/
All your feedback will be welcome, thanks!
Re: Live Sails.js Course
#37Does anyone have any experience with sails?
I've used sails in production on a couple of apps and it's mostly pretty good but there are a couple of annoyances that will inevitably get ironed out as it develops. For me the most irritating thing is being unable to write good unit tests for controllers that use models as sails models are scoped globally and controllers have to be objects which makes injecting mocks difficult. It's great for getting a prototype up and running quickly, but if you're planning on building a big production app, a better longer term strategy would be building an express app from good open source components. (ie using sequelize for ORM). As has been mentioned elsewhere the documentation isn't always consistent and you sometimes find that a waterline function in the documentation has been deprecated in the current stable version, so be prepared to get to know the source well. In any case, it's a great effort and is a great time-saver on getting something live quickly.
Re: Live Sails.js Course
#38Too bad it seems you can only join with Tweeter or FB account.
Re: Live Sails.js Course
#39Does anyone have any experience with sails?
I built my SaaS app backend on sails. There are quite some gotchas left but overall I'm pretty happy with it.
Deep relational fetches would be very very helpfull though, now you basically have to cobble up seperate async fetches to do more complex joins.
Re: Live Sails.js Course
#40Too bad it seems you can only join with Tweeter or FB account.
We're working on more options. Should we include github or an email/password login first?