Hacker News new | ask | show | jobs
by emgee3 3566 days ago
I'm not disagreeing, but one thing that makes this different is you can easily fix most Bootstrap bugs by overriding it with some custom CSS, or just not use that class. It's different than some deeply integrated code that you have to patch and maintain.
1 comments
niftich 3566 days ago
I fail to a meaningful distinction between:

"you can easily fix most Bootstrap bugs by overriding it with some custom CSS" vs. "you can easily fix most [imperative/OO/functional programming language's library] bugs by overriding it with some custom [code]"

and

"just not use that CSS class" vs. "just not use that [method/function/class]"

link
emgee3 3566 days ago
It might be the same, it might not.

An contrived example: let's say an unfixed Bootstrap 3 bug is that there is a formatting error when rendering "div.jumbotron > h1 > span.label > small". You could replace the last small with you own css class and be done.

Contrast that to a bug in Angular, for example, that enabled a XSS bug. You'd want to upgrade Angular, instead of manually patching or adding a workaround to all your forms.

That's what I was thinking, at least.

link