Oh my goodness this is the most cheerful speaker I've ever seen

Would love an updated 2022 version of this talk!

What Vue needs asap, is a React "Fragment" feature, so we can write components that only share state, thus without a redundant root element. This way we can take full advantage of the Render prop method, which in Vue was officially announced as "Scoped Slot". In that regard it's actually pretty funny. While Vue realized this and implemented, React has added "Render Props" to their documentation only recently.

Your energy is great, and there are some very slick patterns in there.

ok so I am 6 minutes in, and this is already one of the best developer talks I've ever heard or watched in my life... those transition animations from previous to new boosts! lol

Two years later, i still come back and learn new stuff from this video

If you don't have time to watch the full talk, jump to 21:55 to Transparent Wrappers because it is a really really cool tip

github.com/chrisvfritz/7-secret-patterns www.patreon.com/chrisvuefritz

Love this video! Will watch again, thank you! Awesome tips and positive outlook. “I’m gonna FIND you and make you learn something if you haven’t” great quote made me laugh 😂

Amazing! First time I got some ”ahaa” moments since started with Vue, thx!

Transparent Wrappers tweak changed my life :D a big big big thumb up on that guy

An amazing talk from an amazing person for an amazing framework. I'm delighted and enlighted by the presentation and by the techniques it introduced. And Chris your positive energy is awesome, I wish I had been given 2x like opportunity for this video. Everything aside dark background for the presentation is killer. Thanks man.

Just a point on Module Registration - I noticed when implementing the directory scraper, that my modules were being added, but everywhere in my codebase that referred to an imported getter/state variable it was erroring. My solution was to add a ".default" after the requireModule(fileName) function call. Just in case anyone should encounter the same fate! modules[moduleName] = requireModule(fileName).default

I knew most of this. Didn't know about `inheritAttrs`, although I did know about `$attrs` long time ago. You can't write a good component without using it. However, using `inheritAttrs: false` on my base component (which all others extend) is a very good practice because it ensures nobody passes down attributes implicitly, which makes the code brittle and unpredictable.

Simply awesome! Thanks a lot!

I'm confused: Why is `.keys().forEach()` working here? When I apply this to an object or array, I get an error that this function doesn't exist. Is this functionality that comes from webpacks `require.context()`?

Great video, and thank you. BUT be alerted: If something needs tips/tricks/tweaks; it should either be redesigned, or requires a new layer to hide all these tips/tricks/tweaks to produce clean and terse code... For example the modules stuff explained in this video. I know the comfort it provides from Quasar. Quasar framework implements this so that I do not need to adjust anything manually. This should be done in Vue from the beginning. Why should I import the modules manually if it can be done automaGically?

This this amazing, wish I knew these tricks earlier. thank you!

So how would you access mapActions using the namespace (what would the spread operator code look like) if you extrapolate your modules into the root level?

Learnt something new, worth watching

28:26 where to put the missing quote at $attrs?

When I use require.context() to load base components globaly I get a warning that say "Critical dependency: require function is used in a way in which dependencies cannot be statically extracted"

awesome, thank you!!

I like his t-shirt... can have one ? please send to Bandung , Indonesia

Thanks!!!

Awesome talk! Thanks for sharing!

Mind blasting!

great! thx man

Wow you are awesome!!!

Good on the Killer Instinct joke. :p

mindblowing 🤯

Looks like a nice guy

So thanks to this, you can now do render-less components. I played with it yesterday and it seems you can't use (Vue 2.5.x) to pass into a slot, it has to be an actual element. Yesterday, this was released: adamwathan.me/renderless-components-in-vuejs/

I'm here because of he Vues on Vue podcast where Chris is now a Panelist! devchat.tv/views-on-vue Fantastic talk!

I‘m not a friend of globals. Explicit is better than implicit. And what about globals in Unit Tests? Global Mocks?!

27:47 "data.dickpic"

Nice mohawk bro

I don't know what I was looking at either lol, probably people moving on the other side

This brought me so many bad memmories that now I realise I had no idea what I was doing.

🤯

Regarding Radical Tweak #2: What you are saying is that Vue breaks on native events, specifically it does not call the native event handler. It breaks but somehow Vue captures that error and keeps it hidden from the developer - then you and Vue decided to spin the fact that this egregious error was hidden by Vue. By calling a Transparent-Wrapper? That is a perfect spin title. Transparent (easy to perceive or detect; clarity) Wrapper (covering for something sold). Yes, sir, you are wrapping the transparency of the situation. That Vue knew about this problem and did not tell it's users, and then chose to spin it with this Radical Hack #2. And called it a Transparent-Wrapper (e.g. Clarity-Concealer). another way to say that is Truth-Hidden. And, a more boiled down version -- a liar.

Of all the things that should be demonetized on youtube clickbait titled shit like this tops the list