News for hackers. Stuff that matters.
Re:Trails – Modern MVC Web Framework for Node.js by smokeyj on Saturday January 02, 2016 @12:56PM (#10826982)
Dismiss it, but you don't have to tell the entire world about your uninformed opinion. It's not as valuable as you suspect.
Re:Trails – Modern MVC Web Framework for Node.js by im_down_w_otp on Saturday January 02, 2016 @01:32PM (#10827195)
Opinion? Both sentences were questions. The first included a hyperbolic approximation (i.e. "50th") and the second included a legitimate direct question that infers an indirect question about the weird pace of churn and factionalization that seems to infect the Node.js community more than any other community.

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"?

Re:Trails – Modern MVC Web Framework for Node.js by smokeyj on Sunday January 03, 2016 @02:46AM (#10829875)
I'm just saying if you have a criticism share it. If your problem is being an nth iteration then that's not really comment worthy. Sure the node ecosystem has an abundance of modules and frameworks. I don't consider it harmful and it seems the developer mindshare sorts through these "problems" with ease.