As long as they look good, are easy to use and have recognizable branding, what is the problem? Say HN used bootstrap with a few small tweaks for colour so it was still identifiably HN. Also your webmail client, hotel booking site & social network. What harm? Isn't familiar look and feel comforting to users?
Is there a good reason for the aversion to looking similar or is it just a product of the history of the web, with everyone doing their own thing?
And glad to hear you're a fan! <3
With that said, I've been using the 2.x releases on multiple projects over the past year. Thanks for all of your hard work!
I am surprised by some of the inclusions such as overhauled grid system to include four tiers instead of the original three of RC1.
To change something so fundamental does seem more like a beta feature than RC1 and no doubt people who've built 2x to 3x converters will be a little more anxious now.
That said I'm sympathetic to the fact that if you're going to change fundamentals or pivot, now's the time. Looking forward to more releases and feature stability.
These aren't complaints by users. These are complaints by developers and designers who often feel a little...perhaps...threatened by bootstrap and things like it.
Okay, I guess it could be users if you cater to those groups, but for the overwhelming majority of cases users don't know and don't care. They find a clean, modern-looking site that offers the functionality and information that they need, and that's all they really care about.
The complaints probably are from devs and designers, but that doesn't mean users like Bootstrap. Devs and designers complain because we know enough to recognize, and complain about, the source of all the monotonous websites coming out these days.
Source of bad design? No. Source of bad taste? No. Source of monotony? Yes, just out of convenience.
Why should every web application look different?
If it was up to me, the browser default styles would be something closer to Bootstrap (and actually implement stuff like the <menu> element), so you can build a decent looking site with touching CSS at all.
That's a remnant of the past and it's changing quickly. Look at any consumer app developed and released in the past year. Most have custom elements, layouts, etc. The web just did it first and is further along in the "designification."
Native apps all looked the same because they were all designed, built, and used by largely engineers. As computing (both usage and development) becomes less esoteric and more powerful, design will naturally become more expressive and purpose-built. This trend extends back to DOS as well and applies well outside of computing (cars, buildings, clothing, hardware, etc).
Your thoughts?
Bootstrap made a big leap with changing the box-sizing though. It was unusable prior to that.
To the devs who feel threatened, I am referring to people who currently sit on a large bulk of custom, in-house code that has been often rendered redundant, if not obsolete, by projects like Bootstrap. I would contest that all front-end devs use Bootstrap or something similar, as the overwhelming majority of devs work on projects with very long lifecycles, quite unlike the common HN manifestation of short-cycle apps.
On a different note: I am a big fan of Bootstrap. Yes, there are tons of complaints from users about sites "looking like Bootstrap", but that's hardly a fault of the framework (at least they look passable). I've always found that some button customisation (easier in 3.0), changing the navbar (color, height, dropdowns) and tweaking the forms is the easiest path to getting a site that doesn't look like vanilla framework. And none of those things require much work or expertise: heck, just a change in height, a different nav-bar font + color go a long way as it is.