Getting to Bootstrap v4
github.com
Getting to Bootstrap v4
1–10 of 43 posts
Re: Getting to Bootstrap v4
#2edit: title changed, thank you.
Development is probably stopping on v3, sure, but that doesn't mean it will completely be unsupported and ignored. Let's say there is some major bug in v3 that comes out soon, you better believe it will be addressed. Otto just wants to push faster on v4 by dropping all existing split dev work.
Re: Getting to Bootstrap v4
#3edit: title changed, thank you. Development is probably stopping on v3, sure, but that doesn't mean it will completely be unsupported and ignored. Let's say there is some major bug in v3 that comes out soon, you better believe it will be addressed. Otto just wants to push faster on v4 by dropping all existing split dev work.
[deleted]
Re: Getting to Bootstrap v4
#4Seems entirely reasonable.
The response to this highlights something I've noticed watching Open Source stuff for a while: this attitude that a piece of software can never simply be finished, but that it must constantly be changing to be alive.
This is a good example of that. Bootstrap 3 has been out for a while and it mostly works for the things it was designed to work for. If you look hard enough, you can find bugs and situations where it's not suitable to use. But that's fine. It's a super valuable thing that we all get for free. The new site I'm building on it looks way prettier than it ever would if I was designing it myself, and will remain so indefinitely, even if these guys never commit anything else to the project.
I don't see anything wrong with the guys who built it stamping it "done" and moving on to the next thing.
Re: Getting to Bootstrap v4
#5On one hand, at least browsers are good about maintaining backwards-compatibility of CSS, so that pages that look okay with bootstrap 3 will continue looking okay for a good time.
On the other hand, slapping "Don't care" label on all the issues of the current stable version seems... bit excessive.
All in all, makes me happy I only use bootstrap for the CSS, and not the JS-based interactions.
Re: Getting to Bootstrap v4
#6edit: title changed, thank you. Development is probably stopping on v3, sure, but that doesn't mean it will completely be unsupported and ignored. Let's say there is some major bug in v3 that comes out soon, you better believe it will be addressed. Otto just wants to push faster on v4 by dropping all existing split dev work.
It's the term @mdo used in other issues like https://github.com/twbs/bootstrap/issues/16913 "Bootstrap 3 is no longer being officially developed or supported."
Re: Getting to Bootstrap v4
#7edit: title changed, thank you. Development is probably stopping on v3, sure, but that doesn't mean it will completely be unsupported and ignored. Let's say there is some major bug in v3 that comes out soon, you better believe it will be addressed. Otto just wants to push faster on v4 by dropping all existing split dev work.
"Should We Stop Bootstrap 3 Support? Probably Not." sounds better?
Re: Getting to Bootstrap v4
#8Seems entirely reasonable. The response to this highlights something I've noticed watching Open Source stuff for a while: this attitude that a piece of software can never simply be finished , but that it must constantly be changing to be alive. This is a good example of that. Bootstrap 3 has been out for a while and it mostly works for the things it was designed to work for. If you look hard enough, you can find bugs…
Generally I agree with this sentiment. Having no previous exposure to Bootstrap's development process, it is interesting to see @mdo acting so unilaterally (and I can see why he is able to after reading his GitHub profile, hah). Particularly considering that he signs off all the issue closures as "@mdo and team". It's hard to understand that (again, as an outsider) without a deeper explanation.
Given that, knee-jerk reactions to the mass closing of issues surely won't come as a surprise, but it also should make for some interesting debate. Is that the best way to stamp v3 "done"?
Re: Getting to Bootstrap v4
#9Seems entirely reasonable. The response to this highlights something I've noticed watching Open Source stuff for a while: this attitude that a piece of software can never simply be finished , but that it must constantly be changing to be alive. This is a good example of that. Bootstrap 3 has been out for a while and it mostly works for the things it was designed to work for. If you look hard enough, you can find bugs…
Right now we don't have a maintained, release version of bootstrap. That's not really reasonable at all, imo. I understand wanting to focus on the next version, but maybe continue to maintain v3 until v4 comes out? Ditching support the day v4 drops is still kinda premature, imo, but still better than this limbo we're left with. Frankly this seems incredibly unprofessional.
Re: Getting to Bootstrap v4
#10Yes Bootstrap4 has been taking too long to the point I wanted to find an alternative.
Maybe a fund-raise to have someone work on it full time, the way like what vue.js does?