4 ms·
Also the rate of breaking changes with react is pretty intense. While you can author react without a build tool, and I certainly am using webpack with vue mysel
by shams93 8y ago
Also the rate of breaking changes with react is pretty intense. While you can author react without a build tool, and I certainly am using webpack with vue myself, your same vue know how also works for spots where you may not have a build tool available, like freelancing updates to wordpress for people for side money. In those cases you're stuck sticking js into a CMS editor. But vue has you covered in all scenarios from the complex app with webpack and vuex to simple reactive code entered into a cms editor without the benefit of a build tool.
- fourseventy 8y agoThats a great point about the CMS use case!
- wolco 8y agoThe rate of change is the biggest issue. If you are not working with react day to day you are at a big disadvanage.
- poxrud 8y agoWhat breaking changes? React's API has been very stable. As of version 16 the entire core has been rewritten without breaking the API.
- richeyryan 8y agoCan you elaborate on the rate of breaking change? As far as I'm aware React's API has been backwards compatible for many versions at this stage. There have been deprecations introduced with React 16 but they don't come into effect until 17 which seems pretty reasonable.