31–40 of 74 posts
Isn't Travis the CEO of balderdash.io? I don't get it... CEO and Founder don't seem to happy with eachother...
Trails will be the replacement for Sails. Modern, maintained, open, and community-run.
Compare the new Trails JS: https://github.com/trailsjs/trails The Trails project is developing thanks to Travis Webb and team, and his reasons are described in the pull request. The Trails README includes this intro: "Trails is built and maintained by former members of the Sails.js core team, and offers an upgrade path from existing Sails applications, but it utilizes exactly zero lines of code from the original Sail…
Yea I've noticed this too, mostly because Travis threw up a comment on multiple GH issues on my Sails library e.g. https://github.com/waterlock/waterlock/issues/99#issuecommen... I've looked over these issues and noticed Travis is just copy/pasting the same message stating "Sails.js is no longer actively maintained". It seems like this guy has a real vendetta against Mike (the creator of Sails) and is dead set on get…
Our company lives off consulting around the open-source tools we build and support. That's it.
Earlier quoted context omitted.
50% increase in development speed after making the switch from what ? I am certainly more productive in Ruby or more recently Elixir than JavaScript on either the client or server.
More productive in the client-tier without using Javascript? I'd like to know how that works.
Didn't the core people behind Sails essentially abandon it for the YCombinator startup Treeline.io? Also, hasn't Treeline been in 'preview mode' for almost a year now?
I remember when I first saw the Treeline demo, I was blown away. It seemed like a great framework for striking web services together to solve problems and build great products. Over the past year, I've become weary of any frameworks that sit on top of Node. I currently run gitignore.io and I've had problems using Kraken.js due to lack of updates to the framework or incompatible dependency maintenance. If I were to go…
At my current one, we are re-implementing a ton of very detailed business logic from a PHP/Cake app, while writing comprehensive functional and browser tests. We considered Sails.js but decided the framework was immature vs. Ruby on Rails.
Rails has worked great for us, and has a ludicrously evolved ecosystem, with fantastic gems available, Stack Overflow answers, and lots of other users filing and resolving Github bugs before us (most of the time).
Rails is not as trendy as Isomorphic Javascript, but Ruby is a pleasure to develop on.
The turbulence with Sails.js makes me feel even better about our choice.
Earlier quoted context omitted.
Node.js is fine. I'm currently contracting for a major company which is using Node.js in production and it's been great. I've worked on Python backends at my previous startup and I can say that Node.js faster to develop with. Linkedin also uses Node.js and they found a 50% increase in development speeds as a result after making the switch a few years ago.
50% increase in development speed after making the switch from what ? I am certainly more productive in Ruby or more recently Elixir than JavaScript on either the client or server.
When you have a company which is split up between frontend and backend teams, this requires your engineers to coordinate their work with one another and this reduces overall productivity (you usually need a lot of back-and-forth to bring the feature to completion).
Earlier quoted context omitted.
More productive in the client-tier without using Javascript? I'd like to know how that works.
ClojureScript, Elm, etc.
Edit: Unless he is only using helpers? Then I wonder how much power he can do with client side applications compared with modern javascript/typescript tools...
I've used sails.js for many (many) projects including gameref.io, hackjob.io, and on several internal projects at my current job. I find it ideal for prototyping and small-to-medium-sized projects. I really hope it doesn't die as I love the pipelined approach it takes. @SignMeTheHELLUp is complaining about Waterline ORM, but I'd argue that Hibernate is worse (and it's an "industry standard"). It's just a fact of life…
> SignMeTheHELLUp is complaining about Waterline ORM, but I'd argue that Hibernate is worse Are you serious. Hibernate and all it's language-specific variants are actual feature-complete ORMs. Waterline falls flat as soon as you get past eager-fetching a child property. It's a toy. I wasn't just complaining about Waterline either. Every time I had issues with Sails I had to dip into the Sails source and patch bugs ou…
Would love to hear more about this - if time permits, would be a great write-up.
Currently a week or two in on a new project using Sails. Any alternatives? Originally, I was going to use just Hapi + Sequalize. Thanks
I don't use sails but I found the criticism of the project interesting because it has somewhere around 80 commits in 9 months. I guess we are in a time where our tools are expected to significantly change frequently? It seems like I have a disconnect with this mentality as we're running products where stability (reliability as well as API stability) and solid documentation are more important than constant innovation.…
> I don't know, perhaps sails is riddled with unfixed bugs? I wrote about a fair amount of unexpected behavior with Sails/Waterline. Some of these have since been fixed, some of them (Waterline defaults to dropping tables unless you have NODE_ENV=production in an env var) are deliberate decisions and hence not "fixable". https://kev.inburke.com/kevin/dont-use-sails-or-waterline/ There's a fair amount of other stuff I…
Whoa, that is bad. If you don't understand what a transaction is, you have no business writing a database library.