4 ms·
Breaking changes such as this makes me rethink what could be the best approach with regards to front end development. I can recall the time when I moved past A
by AngeloAnolin 7y ago
Breaking changes such as this makes me rethink what could be the best approach with regards to front end development.
I can recall the time when I moved past Angular when they introduced so many breaking change on their next version. I started using React but was not comfortable enough to keep pace with its progression. Then I found Vue which was a breath of fresh air as this framework has allowed me to deliver end products faster yet being simple enough to allow for easy scalability & enhancements.
With these upcoming enhancements, I hope that it wouldn’t introduce major changes that would require for me to rewrite large portions of my applications.
I have a lot of trust and confidence with Evan and the Vue Community and I guess all these changes are in line with best practices and better productivity rather than following a path because another framework is doing things like that.
- Androider 7y agoI have a 100K+ LOC project in React started in 2015 that's going strong, and I imagine Facebook has much, much bigger projects than that using React. I can't recall a single time during all these years that something would have broken in a non-backwards compatible way. We're on the latest version of React, writing class-based components (with zero intent to move to hooks) and feeling very good about it.
- scns 7y agoI think Abramov said they habe over 38000 components at facebook, which is enough reason for Thema to keep backwards compatibility.
- acemarke 7y agoA lot more than that - roughly 100K now. Shawn Wang collected comments from the React team over time showing the growth of React's usage inside Facebook: https://www.reddit.com/r/reactjs/comments/btx9nq/reacts_growth_rate_in_facebook_some_datapoints/ https://www.reddit.com/r/reactjs/comments/btx9nq/reacts_grow...
- tohagan 7y agoMeaning you didn't read the RFC which specially states: "Is this like Python 3 / Do I have to rewrite all my code? No. The new API is 100% compatible with current syntax and purely additive. All new additions are contained within the new setup() function. 3.0 standard build will support 2.x options plus the new APIs, but you can optionally use the lean build which drops a number of options while providing a smaller and faster runtime. Details 2.x options compatibility will be kept through the entire 3.x lifecycle." https://github.com/vuejs/rfcs/blob/function-apis/active-rfcs/0000-function-api.md#is-this-like-python-3--do-i-have-to-rewrite-all-my-code https://github.com/vuejs/rfcs/blob/function-apis/active-rfcs...