React Native just dropped a MASSIVE update

preview_player
Показать описание

Follow me on other platforms to stay connected:

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

Updating the library is also important, but I believe we are missing the main issue here. React native packages are the main issue. They have bugs and a very poor maintenance, it needs to be fixed. Expo are well organized and coordinated they have my praise when it comes to that

usmanumar
Автор

A huge slap in the face for flutter lovers who always bully us because of performance 😂

JeanBaptisteChabi
Автор

Thanks for covering the background of the new updates 😊

mdalmamunit
Автор

The first thing Apple and Android needs to do is create this direct binding for javascript natively and kill this whole headache for javascript frameworks. So that react, vue, svelte etc.. can be used without getting messed up in this jargon of bridges and renderers.

jondoe
Автор

Idk why flutter is not catching on as fast. Dart is a powerful language and with flutters rendering engine you can build even video games, so that 60fps was never an issue to begin with. And the dev exp is so smooth. Not to mention you can even build UIs for non conventional screens like thermostats and stuff

TN-kglv
Автор

Flutter is still a better framework but it's nice to see RN is catching up. Huge win to the web devs

iGhostr
Автор

Whats more important is
Flutter is Compiled Not interpreted
So to be honest its just an update
Cannot challenge flutters performance
Flutters directly compiles to Native code while RN is still based on An interpreter
Basic CS: Compilers are faster

syedmujtabaalikazmi
Автор

Thanks for this video. This was an excellent recap on the issue at hand.

Gjacolby
Автор

You explain the things very well ! Liked you explanation . Thanks alot

visheshgupta
Автор

Great video, Great explanation! Liked and Subscribed 🔥🔥🔥

aliarefjs
Автор

Meanwhile flutter:
🗿 for Android
🗿 for ios
🗿 for Windows
🗿 for MacOS
🗿 for Web Apps
🗿 for Linux

abdulcodes
Автор

So it pretty much just removed the bridge middleware and baked in the web component <-> native component mappings. Probably by making it less abstract and more specific at that level of the architecture

tallawahh
Автор

What whiteboard program are you using to explain?

everurstruly
Автор

Well it’s really great that they moved away from the bridge architecture and also the best example of why we shouldn't jump into making things async without thinking it through.

Sandeep-zddq
Автор

Bridge will stay Bridge....flutter --> standalone, independent and better impeller ❤

saharvanunu
Автор

Been waiting for this like forever 😭😭😭😭😭😭😭😭😭

akashdeeppatra
Автор

Loved your explaination bro😮👌.
Can you also make a video on Next.js 15 update and React 19 and the manual AWS deployment with it.😅

noobdotx
Автор

Whats the whiteboard application ? It's simple & impressive

nipunshah
Автор

only 10hrs to hear an update about something you could read of literally 1sec into the video, for 30 seconds, not mins. Update videos don't need a full definition of the entire english dictionary. I lost brain cells trying to find a point here

AtomicPixels
Автор

React: "We some how figured it out to render a list view, with new arch"
React fans/devs: "Wwo now the game is on with flutter"
😂😂

gameStreamerLoco