This Could Change Web Dev Forever

preview_player
Показать описание
A new TC39 proposal for native Signals in JavaScript. What does this mean?

💬 Topics:
- What are Signals?
- What is reactivity?
- Signals code example;
- Signals vs composed signals vs effects.

Рекомендации по теме
Комментарии
Автор

TS as a linter, "Search your feelings, you *know* it to be true."

Fallingstar-yyiv
Автор

1:29 I don't know why I didn't think of binding document.querySelector to document before. Feels a bit like jQuery

antonpieper
Автор

Amazing! We will finally have reactivity out of the box!

eduardoalvarez
Автор

Yes! Please do video on queueMicrotask and JS under the hood topics

zainuldin
Автор

I know it might not be your style of content, but it would be insanely useful to have a tutorial of some kind that walks viewers through how to build their own signals system in JavaScript. At the beginning of my career, I gained so much productivity working with REST APIs after making one of my own. I wonder if the same would happen after building my own signals. Maybe I should be sending this to Traversy lol.

WLockIV
Автор

what is the font used in the code snapshots?

tawsifhaque
Автор

It's just a proposal. It doesn't mean that will be featured in the language itself

DEVDerr
Автор

If I never have to learn [another] framework, this will be gold, Jerry, gold!!

dkazmer
Автор

Please further explain the queueMicrotask

tithos
Автор

JavaScript will have proper monads now

nomoredarts
Автор

I thought Signals is used in classnames in tailwind

SiCrip
Автор

very interested in JS internals deep dives

Rtzoor
Автор

Arg. It’s a library at best. They haven’t even bothered to create an elegant and simple language syntax for it. Object.watch() and Object.observe() was a million times better proposal with much more powerful and useful functionality which a signals library could have been built on top of. It’s a thoughtless proposal. If this proposal is implemented, JS libraries and frameworks are going to become so bloated and polluted with Signal style code.

brnto
Автор

Your presentation is creative 👏🏾. My best part was the "in the beginning God created"😆.

codescype
Автор

It's unlikely that will be implemented because there's no benefit in implenting them in the VM when you can do it effectively in JS. We'll still need frameworks to have nice component syntax and this won't change even if they do implement signals in the VM.

Tomorrow another smart guy will came up with an even better way to handle components and template, and even signals will look like old crap.

Lemmy
Автор

Nice, now JavaScript can inch a bit closer to GDScript.

cariyaputta
Автор

As python dev we are talking for years that signals are antipattern

lhardl
Автор

I'm interested please make more videos, thanks

ahsanabrar
Автор

20years from now maybe it becomes good

botondvasvari
Автор

There is no point in complaining about the framework hell because they all are effects of being on a platform. No one complains about so many programming languages because they don't see the OS as a platform even though it is.
There will never be a single great framework just like there will never be a single great car that we all drive

StingSting