Gregg Pollack - Introduction into the Composition API - Vue.js Amsterdam

  Рет қаралды 6,252

Vuejs Amsterdam

Vuejs Amsterdam

Күн бұрын

Пікірлер: 9
@maaark627
@maaark627 4 жыл бұрын
Well explained, but so much overlapping items that most time important text is not readable :-/
@MudasarRauf
@MudasarRauf 4 жыл бұрын
guys, can you fix audio issues? not very good quality audio.
@substance90
@substance90 4 жыл бұрын
👍 for Gregg's awesome presentation 👎 for the Composition API
@adriatic123
@adriatic123 4 жыл бұрын
Mostly unnecessary additions that complicate clean logic and workflow of a version 2. Thumbs down. Guy said you should use it when your component becomes too large. Well, make more components! Best solutions are simplest no need to add levels of complication
@MyChannel-lz6vz
@MyChannel-lz6vz 4 жыл бұрын
Could you not do this [returning a spread object] in your Vue2 style example? kzbin.info/www/bejne/fHiuoYKCfJhnrqc
@mensaswede4028
@mensaswede4028 4 жыл бұрын
Probably 5% of real-world components can benefit from this new composition API structure. So apparently Vue is going down the standard path of growing into a behemoth in the name of catering to every possible development scenario. History indicates that the result of this is usually a framework that is complicated with a high-learning curve, where only a small percentage of its user community is actually an expert in every area of the framework. My opinion is that when most of the users of a technology aren't proficient in the *entire* technology, then it becomes a lot harder to maintain software over the course of years with the usual developer turnover. Which ironically is the very problem the new Vue composition API is trying to solve. Okay, I'm overstating the case a little bit, but ask yourself if Vue projects 5 years from now are really going to be easier to maintain because of this new API. I'm going out on a limb and saying "no". But, I guess the new API makes the community feel like the technology is active, so a bunch of people will feel good about it.
@scylk
@scylk 4 жыл бұрын
agree with this. Plus, this looks like so much like hooks. If you want this kind of API and Typescript, wouldn't you have a better time going with React instead?
@carlitrosss
@carlitrosss 4 жыл бұрын
honestly most of this seems unnecessary and over complicated
@isimvol
@isimvol 4 жыл бұрын
Amount of coughing in that room..... Curious how many people got sick that day
The evil clown plays a prank on the angel
00:39
超人夫妇
Рет қаралды 53 МЛН
How to treat Acne💉
00:31
ISSEI / いっせい
Рет қаралды 108 МЛН
To Brawl AND BEYOND!
00:51
Brawl Stars
Рет қаралды 17 МЛН
Test driven development with Vue.js by Sarah Dayan
31:07
VueConf Toronto
Рет қаралды 35 М.
Proven Pinia Patterns - VueConf US 2023
31:34
Vue Mastery
Рет қаралды 16 М.
Vue 3 Composition API Introduction [FULL TUTORIAL]
23:46
Academind
Рет қаралды 177 М.
Natalia Tepluhina - You might not need Vuex - Vue.js Amsterdam 2020
22:08
BEST WAY to make Desktop Applications in C++
26:00
The Cherno
Рет қаралды 951 М.
The Return of Procedural Programming - Richard Feldman
52:53
ChariotSolutions
Рет қаралды 61 М.
You’re Probably Using Lighthouse Wrong - Vue.js Live 2023
21:42
Vue Mastery
Рет қаралды 1,6 М.
How to use the Vue 3 Composition API - Beginner VueJS 3 Tutorial
17:04
Modus Create, LLC
Рет қаралды 14 М.
Building Accessible Vue Components
41:03
Vue Mastery
Рет қаралды 6 М.