I have to admit - I had the same reaction that many people had when the function api first appeared ("what is this insanity and why are you breaking everything i love").<p>But I read through, checked out the new (simpler) example, read Evan's arguments about logical task grouping, and on a second read with a more-open mind, I actually kind of like the new syntax and am now looking forward to trying it out.<p>I'm glad they agreed to keep the object syntax around though :)
Reading the comments here and on previous Vue thread, I see a nice example of psychological reactance at play. First, it was "You're going to replace the API? No no don't do this, don't force us to use this new thing that sucks over the old better one!". Now, it is "Oh, so you're not going to replace the old API? Come to think of it, the new API is a really nice idea, has some pretty useful concepts in it!".<p>:).
I think the best part about Vuejs right now is how simple it is and everything just works!<p>A vue component is still as simple as {template: 'hi'}. You don't need webpack or any transliteration for it to work. Just drop the script tag like the good old jQuery and it's working! No wonder it has gained so much popularity as I don't think you can make it more KISS.<p>Transition from vue1 to vue2 was really simple. I just hope that when the dust settles and things are finalized, Vue remains true to it's core of keeping things simple.
As a TypeScript user who always disliked the object API and preferred vue-class-component, I feel a bit left out in the fallout of this. JavaScript users are always the loudest. IMO there is no clear, great option for people who are TS devotees. Again it feels like TS was an afterthought.<p>Will have to experiment a bit. Maybe it's possible to do something decent with some helper functions.
I'm glad they listened, and after reading more into some of the use cases there are times in which having this function api could be very helpful to group certain parts of the code together.<p><a href="https://dev.to/stefandorresteijn/vuejs-is-dead-long-live-vuejs-1g7f" rel="nofollow">https://dev.to/stefandorresteijn/vuejs-is-dead-long-live-vue...</a>
I was pretty worried, both by the deprecation of the Object API, and if the Vue team would listen to feedback on RFCs (and change parts if necessary).<p>Very glad to see that both points turned out well. I was really not looking forward to trying to find/learning yet another JS framework.
Kudos to Evan and the team for listening to the community. There was a big pushback against the RFC, which can sometimes be attributed to sticks in the mud.<p>In this instance, though, I do feel that the changes weren’t necessary. All API changes come with a cost, and I’m unconvinced that the benefits outweighed it this time round.