This makes me glad that I've moved on to Angular Material
How is this any different than the mess between angularJS 1 and angular 2?
Getting to Bootstrap v4
21–30 of 43 posts
Re: Getting to Bootstrap v4
#22Earlier quoted context omitted.
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.
This is exactly the attitude I describe above. Why does Bootstrap need maintaining ? It's a pile of CSS and a few scripts to show and hide things. And it has had three years of effort put in to make sure everything works mostly as it should. That's not going to change. We're just not going to get anything new. It was fine for production use yesterday. What has changed that makes it less fine today?
> Why does Bootstrap need maintaining?
Then why say that you're ending the support for Bootstrap 3? Clearly something IS not going to be done from this point onward, and it's that thing which is worrying people.
Re: Getting to Bootstrap v4
#23Seems 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.
The maintainers of Bootstrap have day jobs. Bootstrap is not the day job. Insisting someone maintain your idea of professionalism in what is essentially a public service they perform in their free time is an odd way to spend your free time. You want bugs fixed on v3? Get off of HN and fix 'em.
Re: Getting to Bootstrap v4
#24Seems 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…
Long time v2 and v3 user - I'm happy to see them mark v3 as 'done'. It's good enough. Bugs exist, but they'll be worked on at a reasonable priority.
I finally moved a new project to v4 alpha for some newer features because I'm tired of waiting. It's not ready for production yet so I'm happy to see this renewed focus for the main devs on v4.
Re: Getting to Bootstrap v4
#25This makes me glad that I've moved on to Angular Material
Until Angular Material makes a similar decision in the future and then switch back to Bootstrap?
They made this decision ages ago in regards to Angular Material for Angular 1.x, and Angular Material for Angular2 is in Alpha.
Re: Getting to Bootstrap v4
#26Earlier quoted context omitted.
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.
Perhaps you should chip in some time or dollars to help maintain a release version. The great thing about open source is that if you care enough, you can help yourself (either directly through code maintenance or indirectly via funding someone else). The only unprofessional thing is the entitlement to someone else's time.
> Perhaps you should chip in some time or dollars to help maintain a release version. The great thing about open source is that if you care enough, you can help yourself (either directly through code maintenance or indirectly via funding someone else).
I wish there was an easy way to crowdfund maintained releases. I've been burned by 3 frameworks moving on with no backwards-compatibility; that was worth money to myself & my business to keep them maintained.
Unfortunately, not enough to hire someone full-time or coordinate it (the original developers in all cases had no interest).
Does this exist?
Re: Getting to Bootstrap v4
#27Earlier quoted context omitted.
This is exactly the attitude I describe above. Why does Bootstrap need maintaining ? It's a pile of CSS and a few scripts to show and hide things. And it has had three years of effort put in to make sure everything works mostly as it should. That's not going to change. We're just not going to get anything new. It was fine for production use yesterday. What has changed that makes it less fine today?
> Why does Bootstrap need maintaining? Then why say that you're ending the support for Bootstrap 3? Clearly something IS not going to be done from this point onward, and it's that thing which is worrying people.
At this point "ending the support" is a semantics fight. When the Bootstrap team here says they are ending the support on v3, they are saying that they are closing issues and PRs that are v3-only and focus on finishing v4.
What they are not "ending" at all is "We still recommend v3 for production and believe it to be stable".
The complication here is the two meanings of "support" of "recommendation to use for your production efforts" versus "we are actively helping a tiny fraction of users with long-tail bug reports".
Re: Getting to Bootstrap v4
#28Seems 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…
Long time v2 and v3 user - I'm happy to see them mark v3 as 'done'. It's good enough. Bugs exist, but they'll be worked on at a reasonable priority. I finally moved a new project to v4 alpha for some newer features because I'm tired of waiting. It's not ready for production yet so I'm happy to see this renewed focus for the main devs on v4.
I agree, v3 can be marked as done easily.
Yet, I understand people having concerns with them dropping support for v3 not having the v4 in a production-ready stage.
But like you said, developers might as well get their hands on the alpha to and see by themselves if the use they make of the library suits their needs and works fairly well. For most people, even an alpha version will probably work fine.
Re: Getting to Bootstrap v4
#29Re: Getting to Bootstrap v4
#30"Bootstrap 3 is no longer supported"... And no final bootstrap 4 release yet. So, there is NO supported stable bootstrap versions at all right now? :-/