I'm so tired of those comments. It's almost always come from those who refuse to research before they talk, only echo what they learned from other people. Do y

I'm so tired of those comments. It's almost always come from those who refuse to research before they talk, only echo what they learned from other people. Do you know why there are new frameworks, new versions every time? Because web is a moving target. New js/css/html5 features are released every day and the libraries have to update to adopt them. Back in the day you do not have css variables, so you have either use sass and do all the math inside the preprocessing process, or crazier, using those shitty css-in-js libraries to calculate css properties on the fly. Nowadays you can pass around the variables and it can cover almost all the case. In able to pass the css property to the component, you need to improve your framework. Another example is html5 history API, back in the old days people implemented link components in SPA with buttons (hilarious but it happened), only after History API is introduced there raised the need to manipulate the history properly, thus another rewrite issued. before that, ES5 introduced `class`, proving yet another way to write js code, which in some situation make cleaner code than the plain old js functions. everything in the web is moving, new nice things are introduced every month, if you want to create a modern and performant web application, you need to keep up with the new fancy things, frameworks are no exception for that.