DEV Community

Kevin Ball
Kevin Ball

Posted on • Originally published at on


3 Key Insights from Vue’s new functional API RFC

On June 7th, Evan You (creator of Vue.js) posted an RFC on a Hooks-inspired function-based API for a Vue.js. It’s an absolutely fascinating read, and well worth going through.

It also sparked quite a bit of conversation and some backlash. I’m not going to go deeply into the conversation, but from my perspective the Vue team has done a great job listening to feedback and using it to improve the RFC.

The only thing I will say is I wish those choosing to weigh in were a bit more respectful. Open source maintainers do a tremendous amount of work for public benefit, and things like RFCs are out there to give you a chance to weigh in and help guide them to what will be most useful. They are not there for you to shit on the work or efforts of those maintainers.

Rampant negativity is pervasive in our community (HN and Reddit both are covered in it), and in my opinion it is harmful. If you find yourself about to make a very negative comment, stop, think about how you can phrase your feedback constructively, and as the old saying goes “if you can’t say something nice don’t say anything at all”. This isn’t to say don’t disagree, but just be respectful of those you are speaking to.

Anyway, back to the RFC.

I think this RFC is worth exploring not just in it’s own sake, but also because it reveals 3 key insights about what the future of front-end development looks like.

1. The future of reusable state management is composable functions

The trend towards component-oriented development has been phenomenal for productivity in the front-end world by allowing seamless composition of independently developed pieces. This has allowed us to create reusable building blocks that we can plug in as needed throughout our applications.

However, efforts to apply this approach to state management have been awkward and verbose. Tools like Higher Order Components (HOCS) introduce extreme levels of nesting complexity while mixins are hard to compose, can have cause namespace clashes, and are opaque when trying to understand where properties are coming from.

React Hooks introduced a new approach that dramatically improved the composability of stateful logic using functions, and this RFC looks like it may take it even further as it manages to remove some of the more unintuitive challenges in hooks (like call order sensitivity and not being able to use them inside a conditional).

2. Types are ever more central to how frameworks are designed

One of the motivating factors highlighted in the proposal and present throughout much of the discussion is that a function-based API makes type checking and type inference far simpler than other approaches.

A 2019 survey by npm found a whopping 62% of npm users (which lets face it is pretty much all JavaScript users) were using TypeScript in some form, with 42% of those writing TypeScript directly and the others using libraries and code written in TypeScript. This was up from 48% the year before.

The trendlines are strong, and types appear to be here to stay.

3. Frameworks are co-evolving along shared directions

One of the things I loved about reading through this was the peak behind the curtain of how ideas move from one framework to another.

This is one of the reasons I think it doesn’t matter too much which exact front-end framework you choose to study - the best ideas get adopted by all of the frameworks, and that adoption curve is happening faster and faster.

There are criticisms about this; part of the pushback against this RFC was that it felt too different from how Vue had traditionally worked. But in my opinion, the cross-polination is a good thing.

This should also help take the stress out of choosing a framework. So long as you learn it deeply enough to master the underlying concepts, you’ll be able to jump quickly to other frameworks as you need to. And if you love the “flavor” of one in particular, you won’t be left out of any big innovations because soon enough they will spread.

Wrapping up

This RFC got me incredibly excited about the future of front-end development. This is not just because I love Vue.js (though I do), but because it highlighted how we as an industry keep getting better at self improvement. Innovative breakthroughs are rapidly spread, improved upon, and adopted throughout the ecosystem. The future is very bright indeed.

If frontend development is something you care about, you might also be interested in my weekly newsletter the Friday Frontend. Every Friday I send out 15 links to the best articles, tutorials, and announcements in CSS/SCSS, JavaScript, and assorted other awesome Front-end News. Sign up here:

Top comments (3)

wanzulfikri profile image

I like this insight:

This is one of the reasons I think it doesn’t matter too much which exact front-end framework you choose to study - the best ideas get adopted by all of the frameworks, and that adoption curve is happening faster and faster.

If more people adopt this view, maybe it’ll lessen the confusion beginners might have when trying to choose between React and Vue.

mattfazza profile image
Matthew Fazza

Very interesting read. Despite not being as well-versed in TS as I am with JS I appreciate the shift towards TS you just described. It seems that the argument for developer productivity had time to mature and become evident in teams' workflow.

To reference another of your points, I like the fact that we're walking towards some unity across frameworks in terms of paradigm (hooks is one of them). It's also cohesive with microfrontends (whatever the future may hold for them).

eimaj profile image
Jamie Allen

Thanks for sharing! I agree that this is a great change for community and the framework.

It's really too bad that this became such an us vs. them discussion rather than a discussion about merits of the proposal itself.. Without this sort of cross-pollination of ideas we wouldn't even have Vue in the first place.

50 CLI Tools You Can't Live Without

>> Check out this classic DEV post <<