Видео

I don't understand why you need to lie to typescript and how constructors protect you from that

Hey, look! The word I always saw on my react traces finally explained

theo thats you?

Effect should have been built into JavaScript. The JavaScript Promise API should have been Effect itself!

The GOAT

Gr8 stack for todo app

Can you please do more video on this? I get stuck on context

Wait, is Ethan living in Theo’s studio? Or did he copy the set? Great video. Although it seems to be that the preemptive model of concurrency used by fibers is ultimately more “co-operative”. Feels to me like the difference is more like “explicit” vs. “implicit”. Like calling “await” is an explicit way of getting concurrent behavior, whereas the fibers are “implicitly” concurrent. Also, why “fiber”? Is it meant to be fiber as in a “bundle” of tasks, like a bundle of fibers?

Masterful. Love your passion.

Your VsCode Theme name ??

damn this is so cool... how do you know so much 😫

Can I ask from where I can read more about this fiber concept? It's very interesting and would like to delve into it more. Great video!!

@ 0:56 Feels like if you had 1st third / last 2 thirds split of your screen where 1st split is words and 2nd split is examples you wouldn't need the cut away and it'd flow better but that's just me. you got the concept, you got the example - those are the ingredients to some good learning pie my man.

what's your network/cpu/gpu/ram/ssd usage program running in the top bar? need that in my life!

hey mr ethan I was reading NextFaster code some of the stuff I dont understand whenever you have time can you please make a video like a long one building it from scratch. thats it thanks

Theo long lost brother?

React doesn’t feel fast. The render model is bad. All this abstraction to bandaid a bad abstraction leaves you with a pile of bad abstractions… no? Every other framework avoids this with a fine grained reactivity model. React should have been rewritten from scratch years ago.

theo looking kinda young today

Interesting, thank you. Side note, the AI suggestions are very distracting

I don't know why, but for some reason all React devs looks same... They even sound similar. It's disturbing as f

Great vid, more of this please!

Great stuff. But please keep mobile in mind for future videos. I can't read the text on the screen

Ethan, blink twice if you're held hostage by an evil skater boi

can't you just split your code in between "setTimeout(0)" calls to free the message loop from time to time? not sure why we would need a second event loop?

react feels fast?

Great vid

Feel Fast is different from being Fast 😂😂😂😂

is ethan stuck in theo's basement?

Keep at it kid, you rock 🎉

Throws at start lazy evaluation about entire function, but it usually means about the arguments of the arguments and they are not lazy evaluated in his code….

I did not see Fast and React in the same sentence for a long time lol

so professional hello?!

Controlled concurrency is huge. Solves a lot of problems I was using queues for

I mean I define non-blocking as JavaScript on a web worker like via partytown. it's literally never blocking the main thread. Id call what you're talking about "concurrency compliant".

came for react, stayed for effect

I know you edit for Theo, but the style is an almost exact copy of his lol. I think it'd be nice to have something more unique. even your intonation in your vice is the same

Hi. It's erroring out when i try to do bun db:push on win11 or macos all latest hw and sw. Thought this was nice to try but oh well.

Q: How easy is it to deploy to Netlify?

what is the variable DATABASE_CONNECTION_TYPE referring to exactly in the .env?

Q: Ethan hi can you update the repo so that everything is using latest version? Can you tell me how you would do that manually so i can get that done asap. Just want to be sure I'm in sync with your thinking process ;-)

Ethan this is simply gold!

Great video, Ethan! You do acknowledge Erlang, but I think the framing could give it more credit. The concurrency challenges you describe-like race conditions, structured concurrency, and managing parallelism-are definitely contemporary issues for many languages, but Erlang and the BEAM VM solved these decades ago. Concepts like message passing, preemptive scheduling, and supervision trees have been foundational in BEAM-based languages since the '80s. What’s being positioned as cutting-edge today has been core to Erlang for over 30 years, so while these are still challenges for many, for BEAM languages, they’re old news!

Thank You So Much !

I am here for the algorithm destruction!

One major Issue I see with Effect lib is the difficulty it has for new devs, I cannot have this code in a small scale company like mine and expect the people working with me to be able to maintain it.

i was here before 15k just letting yall know

Theo should learn to code before opening his mouth

Really nicely narrated. The Effect library syntax is overly complex, if I came across that in somebody else's codebase I wouldn't have a clue what it did without looking it up

Underrated video

Stop with f°°°° to-do-list haha <3