The worst part of react is all the FUD hacker news creates about it every time they try to innovate to make the web's defacto framework better.
359 karma · joined March 14, 2011
The worst part of react is all the FUD hacker news creates about it every time they try to innovate to make the web's defacto framework better.
Their rational was pretty solid in the PR, but seems they overestimated how ready the community is to embrace newer best practices and they are back tracking.
The ROI of this compiler when you consider applying it to the whole ecosystem is mind blowing. Great job react team.
Still not really sure how I feel about class primary constructors on the other hand, will give them some time to marinate.
If you have react experience I really suggest giving modern RN & expo a try.
"In celebration of Marvel Studio’s Guardians of the Galaxy Volume 3, we temporarily re-launched Zune.net last month. We also took the opportunity to fix an issue that was causing some challenges in getting the original Zune drivers to install in Windows 11 with this build in the Canary Channel. So now it should be easier to use your (totally unsupported and still discontinued) Zune on Windows 11."
Some other neat bonuses are:
- Page transitions still use client side routing so it still feels fast like a SPA, and it automatically preserves state on your outer layouts during page changes.
- And something I find mind blowingly impressive is you can refresh the server rendered HTML at any point while the user is on the page while still preserving all of their client side state and scroll position etc. A simple call to `router.refresh()` is all you need to do that, something that would have taken a good amount of API code and shoving stuff into some state management library etc to do before.
1. Back in .net 6, mere *days* before the final release they yanked a hot reloading feature from the dotnet CLI that is typically used by the massively more popular, but free, VS Code, and making the feature exclusive to flagship VS. To me this spoke of a leadership who didn't care about growing .NET with new developers but only to prop up their old creaky VS $50/mo from their established customer base that is locked in to C# from legacy code. They rolled that mistake back but it was a big warning sign / wake up call for me.
2. Speaking of hot reloading, their much touted hot reloading feature SUCKS. It has nothing on the JS guys. Hot reload is a massive deal. How is Blazor ever going to compete with the JS frameworks with a horrible hot reload story. Not to mention Blazor is way heavier in terms of KB and also is way slower rendering performance to boot. Can you even use tailwindcss with Blazor since the compiler relies on your framework being able to hot reload the css changes?
3. .NET MAUI by all accounts is just a massive disaster at this point.
4. Their latest Teams 2.0 UI rewrite is in *drum roll* react.
I dunno it all just speaks of an underfunded / understaffed group at this point whose top brass doesn't care about them beyond the meager, dwindling, VS pro subscriptions they get from them.
https://github.com/pmndrs/valtio
https://codesandbox.io/s/bitter-night-mm4xes?file=/src/App.j...
// a.js
import { proxy } from "valtio";
export const a = proxy([]);
a.push(1);
// App.jsx
import { useSnapshot } from "valtio";
import { a } from "./a";
const add = () => a.push(a.length + 1);
export default function App() {
const snap = useSnapshot(a);
return (
<div>
<ul>
{snap.map((value, index) => (
<li key={index}>{`${index}=>${value}`}</li>
))}
</ul>
<button onClick={add}>Add element</button>
</div>
);
}Regardless I'm sure what you have is a great app here so hope you don't feel like I'm targeting you or your app directly here, and at the end of the day if flutter allows you to make your customers happy more power to you and hope it works out the best for you.