Trails – Modern MVC Web Framework for Node.js • Hacker News Board

Re: Trails – Modern MVC Web Framework for Node.js

#81

Post by mikermcneil » Fri, Jan 08, 2016, 6:45 PM UTC

clay_to_n wrote: post #80

sgress454 wrote: post #73

Earlier quoted context omitted.

What's broken on the website? All the docs on http://sailsjs.org/ work for me.

It works now. It didn't for most of 2015. The index page would send you to broken pages (but if you went to GitHub you could find the info).

Thanks for following up, Clay. Sorry sailsjs.org caused trouble for you last year. You're right-- fixing SEO permalinks in our docs (i.e. converting sailsjs.org from an SPA to a site w/ server-rendered views) was a pretty slow and involved process. This was due in part to the fact that we switched to deeply-nested navigation in the docs, but also because of the sheer number of old links we had to maintain from two different past versions of the website. We weren't able to preserve them all, but we did our best to maintain the functionality of as many legacy hashbang (`#!`) and Angular-style (`/#/`) links as we could. I'm glad to hear the doc links are working for you now.

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

Re: Trails – Modern MVC Web Framework for Node.js

#82

Post by jessaustin » Sun, Jan 10, 2016, 5:14 PM UTC

DonHopkins wrote: post #79

jessaustin wrote: post #55

Earlier quoted context omitted.

Here's one idea: http://cycle.js.org/model-view-intent.html

It's not just about replacing the controller, which nobody understands or agrees on [1] -- it's about getting away from the idea that you can oversimplify user interface architecture down to a holy trinity of just three elemental concepts. You could just as well ask "If Earth, Wind and Fire [2] are obsolete, what replaces them?" There's more to modern chemistry than Earth, Wind and Electricity. [1] http://c2.com/cgi/…

With Cycle MVI can be just a guide for getting started. (More pejoratively, a crutch.) I regularly find the intent()-model() interface getting too verbose and boilerplatey so I just munge the two pure functions together into one. So far it's made sense to keep view() separate, however.

Re: Trails – Modern MVC Web Framework for Node.js

#83

Post by traviswebb » Mon, Jan 11, 2016, 2:33 AM UTC

mikermcneil wrote: post #77

stephengoodwin wrote: post #15

Earlier quoted context omitted.

The last time I checked in on Sails.js about 9 months ago, Mike McNeil, Cody Stoltman, and Scott Gress had just gotten back from YC for Treeline ( http://treeline.io ).[1] [1] https://www.crunchbase.com/organization/the-treeline-company

We are working on Treeline, a tool that compiles Sails.js apps. Our backend is running on Sails.js in production. Fortunately, Travis did not change the Crunchbase page for Treeline. However, he did deface the Crunchbase pages for Sails, Waterline, Balderdash, and me personally (I've since reverted them).

I added them as products to the "Balderdash" company. I think we have different definitions of "deface".

Re: Trails – Modern MVC Web Framework for Node.js

#84

Post by traviswebb » Mon, Jan 11, 2016, 2:40 AM UTC

mikermcneil wrote: post #74

bhanu423 wrote: post #4

Awesome to see a project from the SailsJS team. SailsJS was the first MVC framework which I worked it and was extremely easy to begin with. Kudos for using ES6.

Sorry for the confusion. This isn't a project from us. Travis Webb (@tjwebb) was added as a contributor in mid-2015, but unfortunately it did not work out. The only contributor who was removed from Sails was Travis, in late November. And ever since, he has been doing everything he can to discredit our project, including claiming that the Sails team is working on Trails, or that Sails is "abandoned". Travis is the _on…

> Travis is the _only_ former Sails contributor (i.e. someone with actual write access to our repos)

Again, we seem to define these terms differently. I think if you told the hundreds of Sails contributors that they aren't actually contributors because you haven't given them write access, they would feel rather insulted by that.

> But please realize that this fork is not about technical issues

It's true that I think you're a lying scumbag, but I need a software stack that I can build my business on for the next 2-5 years. Sails.js is obsolete, and these issues stemming from your poor technical competence and community management are thoroughly documented on the internet.