mikermcneil

9 ms·

31.
Work may be watching, but “it might not be as bad as you think”(blog.fleetdm.com)
2 points by mikermcneil 5y ago|0 comments
32.
by mikermcneil 6y ago
For the record, Sails === not dead (unless I am also dead) In all seriousness: I maintain it every day with a team of 4 other core team members with the help of an incredible community of contributors. https://sailsjs.com/a
33.
by mikermcneil 6y ago
“Why does it get hot? Because when the electrons stream through it they bump and jostle their way along like rude boys on a crowded sidewalk. The atoms have to step a bit more lively to keep out of the way.”
34.
by mikermcneil 8y ago
Is it using tweets to backfill “hotness” of a lay/long?
35.
by mikermcneil 8y ago
Have you tried Sails 1.0? (There’s always more to do, but we’re working to improve the framework a little more every day.)
36.
by mikermcneil 8y ago
Why’s that?
37.
by mikermcneil 8y ago
Sorry you feel that way! The rest of the team and I work hard on it as often as we can. But deep populate is not a feature we’ll be adding— Sails and Waterline are opinionated, and I don’t feel that the performance penalty and potential i
38.
by mikermcneil 9y ago
Of course— luckily there are many great, framework-agnostic options for use in post-production. I usually use knex.
39.
by mikermcneil 9y ago
Creator of Sails here. I’d like to set the record straight: The automigrations system is not, and was never, designed for production use. Sails/Waterline documentation explicitly and repeatedly warns against using this feature in pr
40.
by mikermcneil 9y ago
major changes occurred here in 2017 with `await` making its way into the LTS release of Node - more on that: https://gist.github.com/mikermcneil/c1028d000cc0cc8bce995a2a...
41.
by mikermcneil 9y ago
As long as you're on Node >=v7.9, you can also use `await` in Sails, Koa, or any other tool that supports promises. There's some work we had to do to make it feel nicer, and we had to update docs and stuff, but for the most pa
42.
by mikermcneil 9y ago
A lot has changed in v1
43.
by mikermcneil 9y ago
I'm a fan of both Vue and React native. Check out https://github.com/mikermcneil/chatkin for an example app using both
44.
by mikermcneil 10y ago
If I'm running Linux in a VM, I don't think of it as a simplification-- but it is way easier to just shut it off and reinstall if something goes wrong.
45.
by mikermcneil 10y ago
The rest of the team and I are hard at work on the next release, which applies a lot of the lessons we've learned from the beta so far (esp. adding support for loops, control flow convergence, and hotkeys.) We're hoping to get th
46.
by mikermcneil 10y ago
So far, batting way better than chat roulette :p
47.
by mikermcneil 10y ago
Well I mean I guess because you never know what you're going to get
48.
by mikermcneil 11y ago
Understandable-- but if you are productive on Meteor today, or you and your team have already committed to learning about it, I would suggest that you should see that through. This kind of uncertainty/doubt around open source framework
49.
by mikermcneil 11y ago
@rl3 Thanks for the mention :) @maryrosecook I'm glad this post showed up in our Slack feed- really cool topic! As I'm sure you've noticed from the volume, variety, and impressive comments in this thread, improving approacha
50.
by mikermcneil 11y ago
Perhaps, but I can assure you that Express 3 and Express 4 are completely safe. The interface set up by Express is depended on by far too many companies and other frameworks for that to not be the case -- for instance, even though Express
51.
by mikermcneil 11y ago
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 a
52.
by mikermcneil 11y ago
I've posted some additional comments in the GitHub issue to clear up confusion. Hope it helps provide some background on what's going on.
53.
by mikermcneil 11y ago
https://github.com/mikermcneil/waterline2/blob/master/Introd... ^^ after spending several man years of effort on the subject, that's the inevitable boundary in ORM development, IMHO. It was this th
54.
by mikermcneil 11y ago
I'm sorry that this debacle has negatively impacted your opinion of the framework. Other open-source maintainers had warned me in the past that this kind of thing is par for the course as any project grows, but it doesn't make it
55.
by mikermcneil 11y ago
Sorry to hear you had a bad experience. The auto-migration support in Sails is a development-only feature, but for production, there is a great project from Danni Friedland called sails-migrations: https://github.com/BlueHo
56.
by mikermcneil 11y ago
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,
57.
by mikermcneil 11y ago
Travis did not play a meaningful role in the development of Sails. He was a contributor for less than a year and made a total of 37 commits: https://github.com/balderdashy/sails/commits?author=tjwebb That said,
58.
by mikermcneil 11y ago
Certainly you're not alleging that I created that account to write that comment? Not only do I not have time for that kind of dishonesty, Sails was created while I was running one of those "kind of consulting shops". Please
59.
by mikermcneil 11y ago
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
60.
by mikermcneil 11y ago
Also, in case it's helpful, figured I'd mention that we just finished rearchitecting sailsjs.org and the doc compilation process to improve the permanence of links and make the experience of searching for stuff from the docs on Go

More ›