MAmalvikus·Jun 24, 2019
I proposed new Scoped Mixins API (only basic draft ideas), could you looks at this and give feedback - https://github.com/vuejs/rfcs/issues/60
In Vue RFC: Expose logic-related component options via function-based APIs insteadvuejs
rfcs
Web Development2019–2023
vuejs / rfcs
rfcs
RFCs for substantial changes / feature additions to Vue core
15Distinct people
19Mentions
0Explicit recommenders
4.9KGitHub stars
What to know before exploring
What it is
RFCs for substantial changes / feature additions to Vue core
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 12:45:45 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year19 dated mentions
Observed mentions: 2019-02-28 01:12:27 UTC to 2023-09-21 02:07:50 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 9 | 4 | 5 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 6 | 4 | 2 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 3 | 1 | 2 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 1 | 0 | 1 |
What Hacker News says
9 sourcesVue: We no longer have any plan of deprecating the Object API
161 points · Open discussion[I have no affiliation with the Vue team .. just a happy user]
IMHO, composition functions are an elegantly simple and well thought through addition to Vue brought about by a good consultative process. I think this demonstrates that Vue is in good hands with intelligent and wise counsel steering the ship. This small change is nothing like the Angular v1 => V2 experience! No one is breaking backward compatibility!!
Vue is all about coding simplicity ... and although reading through this RFC is at times heavier reading (meaning Evan's team thought through this addition very thoroughly), the final outcome is not! It's uses syntax that is very similar to existing Vue components so if you needed to refactor existing larger components into smaller composition functions, the coding experience is fast and would feel very natural and familiar with
Read the rest
minimal to learn. No one is forcing this additional on you ... its just there if you needed it.
So please before getting spun up on any further misinformation in this thread please read the RFC from Evan You or this very thorough explanation of the RFC which has some nice coding examples.
- https://dev.to/danielelkington/vue-s-darkest-day-3fgh
Is it just React Hooks? ... here's a Comparison
- https://github.com/vuejs/rfcs/blob/function-apis/active-rfcs...
My personal journey
I've coded Angular/Ionic, ExtJS & Sencha Touch, Knockout/jQuery in the past. Learning Vue was nothing like learning and keeping up with these! I was highly productive in Vue in 3 days and the learning curve and documentation was much simpler and lighter so more time to stay focused on the code. I've refactored a legacy boostrap/jQuery web site into nice Vue components in a few hours (impossible with the others!).
I'm absolutely loving the super productive Quasar Framework built on Vue 2.x/3.x which now delivers 130 components, directives and boot plugins with builders for ALL platforms: Web or SPAs (Desktop & Mobile), PWAs, SSR, SSR + PWA, Cordova iOS/Android mobile, Desktop/Electron and dream documentation.
- Check it out: https://quasar.dev
Meaning 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...
In Vue RFC: Expose logic-related component options via function-based APIs insteadVue team lead here.
There is a lot of FUD in this thread so we need to clarify a bit:
- This API is purely additive to 2.x and doesn't break anything.
- 3.0 will have a standard build which adds this API on top of 2.x API, and an opt-in "lean build" which drops a number of 2.x APIs for a smaller and faster runtime.
- This is an open RFC, which means it's not set in stone. The whole point of having an RFC is so that users can voice their opinions. It's not like we are shipping this tomorrow.
For more details, we added a Q&A section at the top of the RFC to avoid further confusions: https://github.com/vuejs/rfcs/blob/function-apis/active-rfcs...
In Vue RFC: Expose logic-related component options via function-based APIs insteadIt's important to note that this is an RFC for 3.x, and they seem to want to provide it for a 2.x revision, and provide a compatibility build, so it's not like angular 2+ where there's no real migration path.
If you have comments, this is where to tell the vue team: https://github.com/vuejs/rfcs/pull/42
In Vue RFC: Expose logic-related component options via function-based APIs insteadVue RFC: Expose logic-related component options via function-based APIs instead
222 points · Open discussionVue RFC: Function-Based Component API
3 points · Open discussion