4 ms·

I think he's referring to all of hipsters who don't really understand what they're using but they're using it because it's hip. Might offend some, but people sh

I think he's referring to all of hipsters who don't really understand what they're using but they're using it because it's hip. Might offend some, but people shouldn't be so quick to hop on a bandwagon and go wrecking working code.

cname 10y ago
And then there are the "retro hipsters" who stick with "vanilla JS" and jQuery (not a framework?), smugly denigrating the new wave of modern "hipsters". Repeat ad nauseum.
- exodust 10y ago
  Might they be denigrating the new wave hipsters on the basis that so many new wave websites are bloated whales on the inside, with pretentious 'mobile-first' machine-pressed skins on the outside? Or perhaps I've just helped you rest your case!
ewjordan 10y ago
It was prototype code, OP said that it was unmaintainable, and complained about, among other things, the "web-boys" adding unit tests - I'm not a 100% coverage zealot or anything, but adding some tests is not exactly hipster shit, it's a perfectly justifiable step when taking a prototype messaging app into production, especially if you have time in the schedule. This does not sound to me like they hopped on a bandwagon and wrecked working code, it sounds like they were trying to bring some fast and dirty code that they didn't like the structure of closer to a style that they were familiar with, which is reasonable. Of course we don't know any real details, maybe the web boys really were a bunch of copypasta idiots that messed it all up - I've seen this scenario play out both ways, and the one thing that's for sure is that prototype engineers are always skeptical of work that other people do on their babies, whether they do it well or not.