Show HN: Million 3 – Optimizing compiler for React
1–10 of 56 posts
Re: Show HN: Million 3 – Optimizing compiler for React
#2Re: Show HN: Million 3 – Optimizing compiler for React
#3Re: Show HN: Million 3 – Optimizing compiler for React
#4Re: Show HN: Million 3 – Optimizing compiler for React
#5Kudos to the team, but why on earth should i choose React when we’ve now reached a point where it needs an optimization compiler, seems silly to be honest.
Re: Show HN: Million 3 – Optimizing compiler for React
#6Kudos to the team, but why on earth should i choose React when we’ve now reached a point where it needs an optimization compiler, seems silly to be honest.
Re: Show HN: Million 3 – Optimizing compiler for React
#7Theoretically, could this be merged in the main React project or would this break something?
Re: Show HN: Million 3 – Optimizing compiler for React
#8Edit: My comment is probably not accurate. Please ignore what I said.
Re: Show HN: Million 3 – Optimizing compiler for React
#9Kudos to the team, but why on earth should i choose React when we’ve now reached a point where it needs an optimization compiler, seems silly to be honest.
Re: Show HN: Million 3 – Optimizing compiler for React
#10I haven't used React in a while and never used SolidJS, but would SolidJS not basically be a optimizing compiler as well for "React". Technically SolidJS is a separate framework and I don't know if it's a 100% drop in replacement like this make be. Edit: My comment is probably not accurate. Please ignore what I said.
Solid doesn't use a virtual DOM like React. Solid is close to Svelte, Vue is in the middle more leaning towards Solid and Svelte today and eventually will be with Svelte and Solid when Vapor comes out and then React is on the other end.
Solid and React do feels similar to the developer because they both use JSX and similar APIs but they aren't compatible.