upvote
I too would absolutely blame a plumber for trying to fix my leaking pipes with a screwdriver instead of e.g. a solder patch. Not everything is a screw, not even in the developing world.
reply
lol Blame the plumber then.

"Infecting with screwdrivers" now see how dumb that sounds?

reply
Blaming React is correct. It is like asking for a picture on a wall and instead getting noisy, power hungry plasma TV on a wall.
reply
I recently began developing an app for Xbox Series X/S. The only framework that will work is UWP. When you look at the UWP docs, this is at the top of the page highlighted "If you are starting to develop Windows apps, we recommend you consider using the Windows App SDK, and WinUI rather than UWP. Although still supported, UWP is not under active development. Please see Start developing Windows apps for more information."

So no, React is a (poor) solution, not the problem. The problem is Windows can't nail down a solid SDK for it's platforms.

reply
Or instead of React you can use native WinUI. So using React is just lazy bloatware introduction
reply
This metaphor is so stupidly bad it's hard to believe you guys even know what React is.
reply
I'm not a dev and actually don't know what React is. I don't care for this metaphor.

As a user, however, I find that the Start menu has become more sluggish than it used to be, and that's pretty annoying. What about that?

reply
Thank you, your comment sure helps to improve our understanding of React a lot.
reply
My bad. I didn't realize it was my job to educate people who talk about things they don't know anything about.

lol what a weird response.

reply
Thanks for adding nothing at all to the conversation.
reply
deleted
reply
We can blame both. If my repair bill was higher because the mechanic chose to use a ridiculous electric screwdriver that used tons of power to achieve what a normal screwdriver can and stripped the screws in the process then I'd also be upset with both the mechanic and the ridiculously inefficient tool.
reply
> a ridiculous electric screwdriver

So React, the most popular front-end library and used my hundreds of thousands of successful apps, is the ridiculous electric screwdriver? See how weird that sounds and makes it obvious you guys can't give an honest assessment?

reply
React is a javascript library. Javascript needs its own runtime. Why not just write stuff in native windows controls and save having to run an entire javascript runtime for no reason?
reply
Only someone who has not tried to write stuff in "native windows" would ask this question. If you want a real answer, go try and develop a Windows native application real quick. I'll wait...
reply
I would hope that the windows developers who are working on the windows shell would know how to write a windows native application in C. If it's that bad, they should improve the API, not just write it all in react instead
reply
I learned Win32 programming from the Petzold book circa 1993.

Pretty much everything in there still works, if I type it in and compile it with the current Visual C/C++ toolchain. I might need to get rid of a few MOVEABLE and DISCARDABLE tags here and there, I suppose.

reply
Windows 7 was not written in react, it looked great and worked great. Get those guys to write the UI for Windows 11.
reply
This is such a ridiculous argument. Applications were developed long before JavaScript was a thing.
reply
> Why not just write stuff in native windows controls and save having to run an entire JavaScript runtime for no reason?

Idk, and I'm not saying it's not a good question, but it's irrelevant to the comparison in OP's comment.

reply
Using an entire javascript runtime and framework to make your OS start menu is using a ridiculous overpowered electric screwdriver that strips heads. Using native windows controls is using a proper manual screwdriver that just works
reply
it's also just a numbers thing. react and more broadly JS developers are a dime-a-dozen as far as availability goes compared to winapi folks.

which on one hand, good -- fuck microsoft and the monolith; on the other hand we get react start menus when we have to use microsoft.

reply
.NET Framework needs its own runtime. Java needs its own runtime.

What's the issue?

reply
I have no issue with user-facing applications doing whatever they want, electron apps bundle an entire chromium to do their thing, but there's a win32 and win64 api in C for a reason, to make OS level stuff fast
reply
I wouldn't want my start menu to load the entire Java runtime before opening, that's the issue at hand.
reply
Its popularity or success in other apps has nothing to with the windows situation.

Other apps are successful despite being slow and bloated, since performance isn’t a primary concern of users. In contrast it’s critical for OS internals like the start menu, so a javascript runtime and framework is just the wrong tool for the job.

reply
"Shit tastes great! Millions of flies can't be wrong!" ;)

React only makes sense as a layer on top of the browser DOM, because the DOM itself cannot be fixed without rewriting it from scratch, so making it usable for non-trivial UI needs to happen in the 'framework layer'.

But without the DOM as the thing that needs fixing and the restrictions of the single-threaded browser-event-loop, the React programming model simply doesn't make a lot of sense. Using the "React-paradigm" outside the browser (e.g. SwiftUI, React Native) is pure cargo-culting, it only makes sense for onboarding web-devs who are already familar with React - but makes it harder to create UIs for anybody else.

The actual problem in the context of Win11 is of course that Microsoft doesn't have any sort of longterm strategy for Windows system APIs (not just UI frameworks). The only long-term-stable API is Win32.

reply
He isn't blaming React (or Copilot), but those who used them in context they had no place in.
reply
"developers with infecting then with React" is 100% blaming React
reply
No it’s directly putting the blame on developers
reply
"I'm on HN and whenever I see React mentioned I'm constitutionally incapable of not saying something dumb"
reply
Seen in the context of the thread, with the both of you never addressing the actual problem at hand but instead reflexively and vigorously defending React against an alleged attack, I'm sorry to say this reads like an admission.
reply
Nobody's blaming React. The blame lies on the bad developers that chose it to write a freaking start menu.

React is the symptom here, not the cause.

reply
What does "infecting them with React" mean?
reply
Introducing bloat.
reply
Umm sir, it's Windows. Bloat is part of its core architecture.
reply
Fair point...
reply