There is no need to always create an "opposite"-view post in response to other "controversial" posts.<p>Can't wait for "The Pragmatic Front-End Developer" to pop-up in a few days.<p>Bottom line, we should focus on discussion that progresses our craft and not superficial rivalries. Take for example the excellent Pure UI by rauchg [1] (at the very least check the first footnote of the article, a true engineer in mind)<p>[1]: <a href="http://rauchg.com/2015/pure-ui" rel="nofollow">http://rauchg.com/2015/pure-ui</a>
Yesterday, when <i>The Boring Front-end Developer</i> was posted, the top commentary[1] seemed generally critical of the change-averse attitude. The TL;DR was "this is technology industry, new stuff is good. Get used to it."<p>Front-end code preprocessors, recent build systems and package managers, new-age frameworks (Angular), "Universal JS", and SPAs would all fit into this category.<p>Some tend to be skeptical, some are evangelists. There is a line in the sand, and while most developers don't fall clearly on either side, taken in aggregate, the line is visible.<p>I quite liked the BFED post. However, I submitted this because I think it makes persuasive counter-points.<p>Given the negative tone yesterday, I thought the crowd here might be more receptive to the more forward-thinking mindset. What's fascinating to me is that, even with nearly directly opposing viewpoints, the commentary on <i>both</i> HN discussion threads is actually quite critical.<p>[1]: <a href="https://news.ycombinator.com/item?id=9879172" rel="nofollow">https://news.ycombinator.com/item?id=9879172</a>
Every time a popular opinion blog comes around that has an opposing opinion come out, I always wonder if these archetypes do actually help to advance the field they're talking about. Meaning, I do actually find it helpful to read about how people are defining their value while performing their skill. Does anyone else find these opposing opinions helpful or do you just see them as wasteful drivel?<p>Granted, this is just a blog post, so the author isn't probably isn't actively trying to craft a faction amongst front end developers.
Somebody needs to concentrate on the boring stuff... in particular, making sure all the stuff on npm etc actually works...<p>The few times I try and use "hipster stuff", like yeoman generators, they don't really work out the box, and it feels like I could have spent that time manually getting things working, also a lot of complexity is added.<p>In a similar way, the churn rate of JS libs is just absolutely insane.<p>From - a boring backend developer.
He forgot the part about jumping on every new JS library bandwagon when its still in beta and impressing all his friends with a new framework nobody has heard of.
One thing the "boring/cool" divide doesn't capture is that a certain amount of the so-called cool kid shit involves an attempt to revive computing ideas that are about 50 years old.