Reactivity: There and Back Again

Rate this content
Bookmark

Everything old is new again. But this time it's different, promise!

This talk has been presented at React Summit 2023, check out the latest edition of this React Conference.

Watch video on a separate page

FAQ

Brunel was known for his radical view against setting strict rules or conditions in engineering, believing that such practices could hinder future improvements. He emphasized the importance of flexibility and continuous advancement in engineering practices.

Front-end engineering has transitioned through several phases, initially focusing on server-rendered pages, then moving to client-side frameworks with JavaScript and jQuery, and recently shifting back toward server-side processing. This reflects a cyclical yet progressive evolution in technology.

The speaker suggests that while technological development often appears to be cyclical, each cycle builds upon previous knowledge and practices, leading to gradual improvements and innovations. This concept is described as 'spiraling' into something larger and more refined over time.

Immutability and mutability are approaches to state management in programming. The discussion highlights a shift from mutability to immutability for cleaner and more efficient code, and then a reintegration of some mutable concepts when beneficial, showing a balanced and evolving approach to managing state.

Modern web frameworks are increasingly incorporating reactivity in a predictable and efficient manner. Frameworks like Vue, MobX, and Solid have advanced the concept of reactive programming to ensure that applications are responsive and efficient without being unpredictable or unreliable.

The speaker anticipates further integration of reactivity across network boundaries, such as with React Server components and new frameworks that allow reactivity to extend from the server to the client seamlessly, potentially standardizing how reactivity is handled across platforms.

Eisenbart Kingdom Brunel was a renowned civil engineer known for his groundbreaking projects like the first tunnel under the Thames River, the big bridge near Bristol, and the largest ocean steamers of his time. His contributions significantly advanced the field of civil engineering.

Michel Weststrate
Michel Weststrate
12 min
02 Jun, 2023

Comments

Sign in or register to post your comment.

Video Summary and Transcription

The Talk discusses the cyclical nature of technology evolution, with examples from civil engineering and software development. It explores the shift from serverless to client-side frameworks and the recent move back towards server-side processing. The evolution of technologies and states is examined, highlighting the progression from mutability to immutability and the introduction of observable immutability. The future and next generation of reactivity are also explored, with a focus on the blurring boundary between server and client and the importance of embracing uncertainty and avoiding dogma.
Available in Español: Reactividad: De ida y vuelta

1. Everything Old is New Again

Short description:

I'm going to talk about everything old is new again. 200 years ago, the whole new technology field of civil engineering. Eisenbart Kingdom Brunel, the best civil engineer of all time. He built loads of stuff, including the first tunnel under Thames River, the big bridge near Bristol, and the biggest ocean steamers of the time. AI is about to get our jobs. React components were reading from the database in front file system, but apparently, they moved back to the server. Are we now back to writing PHP? Are we going in circles? I think that's not the case.

Good morning, everyone. I'm glad to be back here. And I'm going to talk about everything old is new again. You know my passion is reactivity. So I'll be telling a bit more about that but first I will go to an entirely different story. An entirely different era, actually.

200 years ago, the whole new technology field of civil engineering. And it was changing all the time. They invented steam engines, and ships, and trains, and stations, and railroads. And why one guy became particularly famous. Because he was probably the best civil engineer of all time. And his name is Eisenbart Kingdom Brunel. And what made him so great? I give you three reasons. First of all, he built loads of stuff. He built the first tunnel under Thames River. He built the big bridge near Bristol. He built the biggest ocean steamers of the time. And also, he dressed himself properly. So, sadly, we didn't stick with that tradition, if I look at myself, you all. But I think we can learn something from that. Thirdly, he had the most profound, eloquent quote about programming. Now, you might be wondering, what is that quote? I'll tell you in a bit, so stay tuned.

Meanwhile, while I was reading up on civil engineering, a lot of things changed in the front-end world. So, first of all, apparently, AI is about to get our jobs. Secondly, this thing happened. Suddenly, we had React components, and they were reading from the database in front file system. Apparently, they moved back to the server. And so, are we now back to writing PHP? Anyway, like, if I combined those two things, I'm not sure if that's a good thing or a bad thing. Not sure to hate the AI or pity it. In other words, are we going in circles? And I think that's not the case.

2. The Loop of Technology Evolution

Short description:

I think what's happening here is very interesting. We started with serverless things and server-rendered pages. Then we added interactivity with JavaScript and jQuery, but it got out of hand and we built a client-side framework. And now we're moving back to do more on the server. Is technology just going in loops?

I think what's happening here is very interesting. I mean, it's very easy to joke about it, but this is serious stuff. So, if I look at front-end engineering, how I know the evolution of it, as we started with all those serverless things, server-rendered pages, then we sprinkled some interactivity on top of it with some JavaScript, jQuery, and then it got out of hand and we built a proper client-side framework. And now we're making the move back again to do more on the server. So, it makes you wonder, is technology just going in loops? And this loop seems now to be closed, almost.