Earlier quoted context omitted.
I'll give you an upvote because I hear what you're saying; keeping up with new browser features is tough if you've got other things to do as well. But, you don't need to incorporate every new feature into your own web projects, and you don't need to follow the same rapid release cycle as the browsers. If my project has an annual update cycle, I want to be certain that any new browser features I'd like to use are wide…
But, you don't need to incorporate every new feature into your own web projects, and you don't need to follow the same rapid release cycle as the browsers. Sure, but then if the features aren't going to be incorporated into new projects almost immediately, browsers don't need to push out new releases (and the attendant risk of regressions) every few weeks either. The biggest claimed advantage of the rapid release cyc…
I do agree with your points about the rapid release of browser bugs alongside the new features. I've had multiple occasions where clients have told me "You changed something and broke the site" on a project I haven't been working on, only to find out it's only broken in Chrome. My response to them that it's a bug in Chrome that's been reported, affects lots of websites, and will probably be fixed in a few days/weeks, and there's little or nothing I can do about it, is never satisfying.