If anything, this gives them the chance to start anew, equipped with the knowledge of past mistakes, to avoid making them again.
That said, I wish Trails the best-- I just think it's important to point out information that is being misrepresented.
If you have any technical issues with Sails, I would appreciate hearing about those on GitHub.
If the implementation of the Sails as a Rails-like JS framework was as bad as he says, be shouldn't use it for his next project.
A bunch of members of the community apparently had similar thoughts. As long as the idea of Rails-like JS framework isn't fundamentally flawed, they seem to be doing the logical next step: make something better.
It was only just this morning with the attention from Hacker News that we learned about the similarities between the two logos/brandmarks, and we're actively coming up with something new and different.
We'll keep the community posted on the status of the new designs here: https://github.com/trailsjs/trails/issues/47
Being open, compassionate, and transparent is a huge part of what we're hoping to do with Trails, so chatting with us directly is always an option.
We hope to see you on gitter!
All best :)
I'd hitherto not heard of tent nor seen their logo, and neither had anyone else on our team. Saying that we "stole" it is fine for sloppy internet-talk, but it imbues your statement with a level of accusatory malice that we should try to avoid.
If every other month a new thing was made, marketed, HN'd, and Twitter-culted that did basically the same thing as Nginx but had a slightly different config file format or shared-object handling mechanism or some other random detail I'd think that was also weird and somewhat superfluous.
It makes me wonder if building MVC frameworks has become so technically rote (time investment notwithstanding) that the simplicity of it has pushed them into Parkinson's Law of Triviality territory, such that everybody has their two-cents on how this weird metaprogramming trick is better than this other weird metaprogramming trick so now I can write my routes and handlers in this shape of quasi-DSL instead of that other quasi-DSL, and so then goes and makes a whole "new"... sorry... "modern" MVC framework.
How far away are we from realistically being able to replace the idiom, "bike-shedding" with, "MVC-frameworking"?
Don't get me wrong, Sails might be very good for prototyping something, but I could recommend it only if your only goal was to prototype something.
I do have quite a few other issues with sails and waterline (ORM). Waterline provided lifecycle hooks, but limited their power and had poor documentation on extending them. Same for sails core itself, it had hooks for writing modules and extensions, but no one outside of the core team knew well how to use them. As for migrations I ended up doing all of my own migrations with knex, I'd love to see knex or sequelize be the core of a new ORM, rather than a quickly cobbled together sql module.
Trails has promised something better on a lot of these fronts through modularity, I hope they deliver.
We also owe Kevin Burke from Shyp a big thank you for drawing our attention to the SEO problem in the first place. Regardless of where Shyp goes with their tech stack long term, it has been immensely helpful to learn from Kevin's experiences using the framework there. Those lessons have already impacted the direction of Sails, and will continue to influence its future development.
On the subject of documentation, I wanted to share two other resources from 2015, in case either of them might be helpful for you: The first is a free Sails course on Platzi (https://courses.platzi.com/courses/develop-apps-sails-js/). It covers best practices for authentication, blueprints vs. custom actions, and multi-instance deployment to Heroku, and contains some great Q&A. The second is "Sails.js in Action" (https://www.manning.com/books/sails-js-in-action), a Manning book about Sails written by Irl Nathan (creator of Sailscasts) and myself. It is set to be published this Spring.
Finally re: the next generation of Sailscasts-- I don't want to speak for Irl there, but I should point out that there are 6 episodes of the second series of tutorials available (https://github.com/irlnathan/activityoverlord20). You can also see the final example app that Irl and I worked on together which includes a reference implementation of present/idle/away/offline status, user login, and chat here: https://github.com/balderdashy/activity-overlord-2-preview
You might also want to check out sails-db-migrate: https://github.com/building5/sails-db-migrate
At Treeline, we're using sails-migrations in production.
A newer framework from the same people has at least one thing going for them: they aren't likely to make the same mistakes.
Just no. I was working with Sails.js for about a year now on production systems - it's horrible. Without a doubt I can say that it's the worst framework I've ever worked with. Especially their so called "orm" - we actually had to switch it off and work with pure mysql queries instead because it can't even do migrations (it deletes everything from db, stores in ram and re-insert).
Seriously, don't believe the hype, I bet this will be just as bad as Sails.