Eskimo – Node Boilerplate Framework for Rapid MVPs

  • I do give some props for productivity and sharing a solution with the community (rather than just bitching about other peoples' solutions).

    This looks pretty well-put-together to get a project started quickly, though my personal preferences might have been sass/foundation. To me those are small nitpicks in the scheme of things, and you're never going to be able to please everyone with your choices for defaults :D

    The checkmark tables get under my skin a bit since they're mostly a specific set of dependencies (which of course your framework 'aces') rather than a comparison of actual features (in fairness, asset pipeline/DI I'd consider features).

    Anyway, this is neat and looks worth some exposure. Keep on hacking!

  • I've iterated twice on these kinds of projects. First was Drywall and the latest is Frame. Drywall includes a front-end and Frame is just an API. Finding a happy medium of features is tricky. Some choices limit your audience quite a bit.

    Drywall [https://github.com/jedireza/drywall] Drywall is limited to people who're ok using Grunt instead of Gulp or Backbone instead of _______, etc...

    Frame [https://github.com/jedireza/frame] I created Frame to appeal to a larger audience. And because all the front-end opinions were removed it plays nicer since you "bring your own front-end". Interestingly enough, now I'd like to provide Postgres as well as Mongo db connections.

    In general these projects are interesting and I think serve best as examples of apps beyond the absolute basics. Once you make an app yours, it'll probably go in it's own direction quickly.

  • That title looks like something you'd see in a HN parody.

    Serious question though: why "Rapid MVP" instead of just "MVP"? I thought the whole point of an MVP was that it required less time and effort - the rapid seems redundant to me. Am I missing something?

  • Does it have sequelize support?

  • Another cheery day on HN, post a framework debut and people just bitch about some PC nonsense related to the name and other semantics. On a positive note it seems like a good idea and direction to go in, thanks for your work on this, as a Sails user I will be watching developments

  • In Canada "Eskimo" is often considered an offensive term. The term is widely taken to mean "raw meat eaters" which is understandably offensive, though it may actually have come from "snowshoe-netter" which doesn't seem so bad.

    I'm sure the project maintainer isn't aware of the controversy, but he or she should consider changing the name. A fledgling library needs all the help it can get with getting hung up on something so unconnected.

  • FYI, as the Wikipedia article linked on the site states, in some place (e.g. Canada), the term "Eskimo" is considered politically incorrect (along the same lines as "Indian" as a term for native Canadians or Americans).

  • Why the hell would you choose LESS when it's so much worse than both SASS and Stylus.