everyone should make their own framework in vanilla js , you're already dependent on the js language , why become dependent on 3rd party libraries and companies? i don't see why one would love more abstraction, as a programmer you interact with hardware and manipulate it so don't forget that, the C language is still the best representation of what's happening under the hood

Helpful

❤ finally

idle, prepare - ??? nice deep dive in Node.js 😂👍

I Love him in BLACK

the new "react"

amazing..... superb talk and in-depth.

that is awesome

stopped watching after i heared "php isnt dead" lol xD

Thank you.

learned a lot from this talk!

A very good explanation.

very concise and clear to understand, very helpful conference, thank you

The hardest thing about framework free is finding the right search term to find the topic by. I'VE BEEN LOOKING FOR THIS!

Awesome talk! Thank you

Great stuff, man. Thank you for this

git repository of these examples would be appreciated

The greatest one with the greatest and enough full examples! the only question which remains why `Promises queue` takes priority over `process.nextTick` after getting into `Promise.queue`, is it because of `Promises` are inside `V8` and `process.nextTick` is part of `Node` ?

so you're telling me i Can't use postgresql yet for serverless cloudflare workers ?

What is that music at the starting?

At seventy mile an hour on the freeway that is

Audio is bad

What an insightful talk. Thanks so much!

Amazing presentation and presenter. Clear delivery, clear slides.

Great talk! I'm also trying to make the world a better place through learning JS in order to help me achieve my ultimate goal of sharing with people about the hope and transformation Jesus makes in your life if you repent and believe in him!

Great educational video. Thank you! I wish we had to use only synchronous code with the ability to run it in parallel (or pseudo-parallel).

I solved this problem by Async Tree Pattern

Thank you so much for this talk! ❤

Is it posible we can get this sample codes and images

very useful

thanks for the talk Kyle, based and JSpilled as always

Well,... don't get me wrong. It's a great presentation, nice delivery, but the content is pornography and you should view it as such. First understand the problem then understand the proposed solutions. The thing that I am trying to convey is _in software development there is no substitute for thinking_. No amount of _do this don't do that_ is going to make you a better, or even a decent programmer. Those are training wheels for juniors.

You nailed it, For me, the best and most accurate explanation for eventloop.

I did not understand why setImmediate callback always executes first if it is called from thread pool callback. It kind of does not make sense. I thought it would also create a callback that would be executed the next loop after timers, but somehow it looks like it doesn't wait for the next loop, when created within the thread pool callback

'promo sm'

Great presentation

15:13 It's easy. As a rule of thumb, innerHtml is slow because the browser needs to reparse the html (even though it is being set to '' ). element.removeChild , however, directly modifies the DOM without any parsing needed. Therefore removeChild is faster.

Great presentation. Asynchronous coding is hard -- it's counter-intuitive and has many edge cases -- yet we have to deal with it day-in and day-out. The last thing we needed was yet another syntax. Especially one that doesn't add any new capabilities and comes with a whole bunch of brand new edge-cases. Also loved the outro. Promises were a great syntactical improvement over callbacks but they're a woefully inadequate primitive compared with other async primitives.

Good overview and advice here. useEffect is both counter-intuitive and a big foot-gun. It's not (just) that the docs are misleading but that it was badly designed and probably should have been "baked" longer before releasing it to the public. The Hooks API is syntactically nice (shorter, setup and cleanup are colocated, and explicit-ish dependencies), but semantically they are a nightmare (heavily dependent on React's internal scheduler (which nobody is familiar with and isn't obvious from general JavaScript knowledge), inconsistent use of variable closure, inconsistent execution semantics for hook arguments, no explicit dependency notifications, plus all the usual pitfalls of JavaScript's equality comparison. Hooks that wrap or depend on other hooks only aggregate all those drawbacks. I fear the Hooks API is the beginning of the end for React.

0:00 Imperative vs declarative code 4:00 React is not unidirectional 5:30 React is an MVC framework 6:42 Imperative doesn't scale 7:55 Imperative violates separation of concerns 8:46 Overview 9:15 Declarative code is less buggy 9:30 Declarative code is easier to debug 9:47 Declarative code is easier to understand 10:10 Declarative = reactive = unidirectional 10:41 Flux async/effects aren't unidirectional 11:02 Redux's syntactic Grand Canyon 12:12 Imperative code, tempting dead-end 13:07 Declarative needs easy tools 15:03 Have a declarative mindset

The example at 10:05 is not how fetch works, it returns a promise, .json will fail

Thanks UtahJS for having me! It was a great Conference!

Indeed, these are things which every developer should know despite their level of experience.

How can I get access to these slides?

Awesome talk 🤩

Great Video! Super proud of myself for being able to predict most of the deterministic results. Seems like my goal to solidify my node js understanding is paying off 😌

Nit: in the "blank canvas" code, a self-closing tag like "<body />" is valid only in XML, not HTML. It should be "<body></body>".

Hey Warren. Awesome presentation. Where could I find the source code ?

24:28 :D :D :D :D :D :D :D i'm cracked up :D