Vue RFC: Expose logic-related component options via function-based APIs instead

Post by tnolet » Thu, Jun 20, 2019, 10:22 PM UTC

dmix wrote: post #27

tnolet wrote: post #16

I might be totally and completely wrong, but changing everything does not help anyone except scratch the itch of the framework's designers. I'm pretty sure this is all with the best intentions, but this would be a disaster similar to how Angular suddenly changed everything . Not against change, but the API is fine. Just iterate and evolve it. disclaimer: Big fan of Vue, early user and conference attender..

The page mentions providing a compatibility build: > “The proposed APIs are all new additions and can theoretically be introduced in a completely backwards compatible way.” One thing they want to avoid is the whole Python 2 vs 3 distinction that went on forever. I’m not entirely sure these differences are that significant but having to merge in all of the data/computed/watch etc options into a single setup() function…

Post by elwayman02 » Thu, Jun 20, 2019, 10:25 PM UTC

mharroun wrote: post #30

Why don't they just call it a new framework if its undergoing such a major overhaul. This only makes me feel better about picking react at my current company as now I view this framework as dangerous for building anything long lasting.

Post by drenvuk » Thu, Jun 20, 2019, 10:25 PM UTC

Post by quickthrower2 » Thu, Jun 20, 2019, 10:26 PM UTC

pier25 wrote: post #11

KukicAdnan wrote: post #5

I always saw VueJS as a successor to AngularJS in that it followed a lot of the same concepts/syntax/etc. that made it really easy to jump into. Now Vue is maturing and becoming more Angular/React like...so it's only a matter of time before another framework comes out that replicates VueJS2/AngularJS in being super easy to jump into and just write code and the cycle repeats.

Svelte?

Post by ng12 » Thu, Jun 20, 2019, 10:26 PM UTC

pier25 wrote: post #21

chupa-chups wrote: post #2

@Vue team if anyone should read this: I'd recommend to rename vue in the process (for example vueNG or whatever) in order to reduce the amount of false/outdated information when searching for a topic.

Yes, that's what the React team should have done when they implemented hooks.