I think if we just went over to compiling and having the compiler optimize before the code even executed it would go a long way towards fixing Everything that is ultimately wrong with javascript.
If we are using a compiler now, Why doesn't react just switch to running components once and update the dom nodes directly only when state and props change?? just like how solid does it??
I feel react team needs to re-architect the APIs. They can adopt from other frameworks. People use react because many companies are using it and it helps in getting job.
1:30 Can the compiler automatically prevent developers from writing code this bad? So much for "declarative rendering framework" 2:20 React cares more about performance can code quality. 180° from its beginnings.
This is the first time ever I'm uninterested in a react innovation! They are inventing patches to make up for their mistakes in API design. I hope they are trying to invent a lightweight framework that offsets most work during compile time like solid js.
Why should they do that since Solid already exists? It's a different set of first principles, they are not the same. React Forget is an experiment worth doing.
meh... whats wrong with standard JS, HTML, CSS, its more simpler, standard and straightforward... anyone who need framework to do web are coders who lack of skill to do the actual coding... framework are the way to do simple thing so complicated...
Javascript is very much not standard, there's many different standards in javascript just looking at a functional paradigm vs OOP, and when you get to actually writing either one there's still too many ways to do anything. It's not simpler at all when you have so so much extra code that a framework would just put behind a screen. The dev experience of building a vanilla project is uninanimously unscalable and very frustrating. You have to build everything by hand and brick, instead of using drills or workers.. very inefficient..
I very much agree with you. An original idea behind React was mentioned in the first part of the presentation -- "UI is a function of data". React strives to be declarative, which is not what DOM API supports.
Yes it's absolutely doable to build web using Vanilla JS, but in large apps things might get outta hand, Library or Framework like Vue, Svelte and React exist to help developers in building those apps, well in a nutshell they only exist because they want developer to have easier and more enjoyable developer experience
Can’t wait to look at the compiler code
Hyped for this 🎉
coming from the blog
react forget compiler is jusr awesome...we will never have to write manually memoize ever again!!
Thank you.
looking forward to use it in projects
Hopefully the performance gains will be even better when this is release.
I think if we just went over to compiling and having the compiler optimize before the code even executed it would go a long way towards fixing Everything that is ultimately wrong with javascript.
I remember seeing Xuan Huang video 2 years ago about this, I didn't think it will work.
Curious, i thought useEffect would also solve the problem. Anything that i missed? I'm new with react
Does anyone know if React Forget is going to optimize only React code running in strict mode?
Yes please, this will be actually a bug fix of developer UX for me.
If we are using a compiler now, Why doesn't react just switch to running components once and update the dom nodes directly only when state and props change?? just like how solid does it??
Because that if/else outside of JSX wouldn't work. It's a different mental model.
You can with Signals
optimize UI-render base on compiler vs runtime, both will introduce extra runtime cost.But which is better?
Didn't they say in the presentation bundle and runtime cost were minimally impacted by the compiler?
I think that's why Instagram web crashes after being open in the background for a certain time.
Okay, I got the idea of this video: the main idea of this video is to give us more reasons to choose another lib/framework.
Why do you say that? Is automatically memoizing things bad in your view? Actual question - I'm trying to understand why this would be a bad thing.
I feel react team needs to re-architect the APIs. They can adopt from other frameworks.
People use react because many companies are using it and it helps in getting job.
1:30 Can the compiler automatically prevent developers from writing code this bad? So much for "declarative rendering framework"
2:20 React cares more about performance can code quality. 180° from its beginnings.
what's so bad about that code?
obviously it's not performant and somewhat iterative but it doesn't seem awful if you boil everything to a .filter and add some useMemo's ?
This is the first time ever I'm uninterested in a react innovation! They are inventing patches to make up for their mistakes in API design. I hope they are trying to invent a lightweight framework that offsets most work during compile time like solid js.
why not design and implement your own framework 😂
Why should they do that since Solid already exists? It's a different set of first principles, they are not the same. React Forget is an experiment worth doing.
meh... whats wrong with standard JS, HTML, CSS, its more simpler, standard and straightforward... anyone who need framework to do web are coders who lack of skill to do the actual coding... framework are the way to do simple thing so complicated...
Javascript is very much not standard, there's many different standards in javascript just looking at a functional paradigm vs OOP, and when you get to actually writing either one there's still too many ways to do anything.
It's not simpler at all when you have so so much extra code that a framework would just put behind a screen.
The dev experience of building a vanilla project is uninanimously unscalable and very frustrating. You have to build everything by hand and brick, instead of using drills or workers.. very inefficient..
@@3pleFly there is difference between library and framework, what u said by drills is a library, framework is like prefab house
I very much agree with you. An original idea behind React was mentioned in the first part of the presentation -- "UI is a function of data". React strives to be declarative, which is not what DOM API supports.
Yes it's absolutely doable to build web using Vanilla JS, but in large apps things might get outta hand, Library or Framework like Vue, Svelte and React exist to help developers in building those apps, well in a nutshell they only exist because they want developer to have easier and more enjoyable developer experience