Ah gotcha. So it’s not strictly correct to call the whole start menu a react application, just a part of it that always loads when you press the start button.
I’m all for being correct, but MS absolutely deserves being clowned on for this.
In the end, every time you use your start menu you have to load the react crap. At that point, they could have done the whole thing in react with the same ramifications. I am all for correctness, but in real life use the start menu is visibly not working as it should, regardless of the element that is actually causing the issue here.
Is it? Once you have committed to showing “content from around the web” you are locked into spawning a web view. Then you might just as well use js for the web view bits.
The real issue is embedding a browser on the start menu to shove stupid drivel at your eyeballs. Using js to do it seems like a decent engineering practice.
No you aren’t. There are a million ways you could handle this that don’t require a web view. Saying that means anything that retrieves any information from a server needs one. All it needs to do is retrieve the information that needs to be displayed from a server. I don’t know what all they serve through it, but it could easily provide the text and images needed without a web view.
Displaying web content is a business requirement, not a technical one. Everything follows from there.
Besides, they need full JavaScript to allow the partners to inject tracking code to make sure they are getting to what they paid for. You. The product.
Well sure. If the requirements are stupid then they’re stupid. That’s not what you said before though. Showing content from the web doesn’t create stupid requirements.
I said “content from around the web”, in quotes. It’s what Microsoft calls this feature, that originated in Edge collections and spread like a plague over a bunch of UI elements.
It’s ok if you don’t know things. You don’t have to be a jackass about it.
I upvoted your reply until I got to your last sentence. I haven’t been rude. Why are you being rude? Meanwhile telling me not to be a jackass about it…
Yes, a hodgepodge of shit is of course worse. But fucken say that then. Dont say, “its literally a react native application! Thats why its so bad!” when that is not true and sounds ignorant.
Personally, I am 100% grateful for this correction, because I didn’t know and since I’ve heard the less accurate ragebait version dozens of times at this point I would have been confused, next time I have to spin up a Win11 image, why I couldn’t replicate the spike I’ve heard so much about. The fact that it’s tied to a particular UI component, one of many that machine provisioning scripts and playbooks commonly disable, means it would have remained a bothersome unresolved mystery to me forever if not for your comment. So thanks.
Oh it still spikes without the recommendations lmao at least my work laptop was because I, too, have all the bullshit registry entries to make Start Menu usable and resource monitor was showing 10% spikes on average each time I opened the start menu. Wild.
Its only the recommended section thats written in react.
https://youtu.be/kMJNEFHj8b8
We got plenty of real things to clown on Microsoft with. We dont need to make shit up. This is just rage bait.
I try not to let such considerations get in the way of posting excellent ragebait.
Ah gotcha. So it’s not strictly correct to call the whole start menu a react application, just a part of it that always loads when you press the start button.
I’m all for being correct, but MS absolutely deserves being clowned on for this.
So let’s clown on them for the 10% spike, let’s not say that its because its 100% react when its not.
In the end, every time you use your start menu you have to load the react crap. At that point, they could have done the whole thing in react with the same ramifications. I am all for correctness, but in real life use the start menu is visibly not working as it should, regardless of the element that is actually causing the issue here.
That’s actually worse. You do get how that’s actually worse, right?
Is it? Once you have committed to showing “content from around the web” you are locked into spawning a web view. Then you might just as well use js for the web view bits.
The real issue is embedding a browser on the start menu to shove stupid drivel at your eyeballs. Using js to do it seems like a decent engineering practice.
No you aren’t. There are a million ways you could handle this that don’t require a web view. Saying that means anything that retrieves any information from a server needs one. All it needs to do is retrieve the information that needs to be displayed from a server. I don’t know what all they serve through it, but it could easily provide the text and images needed without a web view.
You misunderstand.
Displaying web content is a business requirement, not a technical one. Everything follows from there.
Besides, they need full JavaScript to allow the partners to inject tracking code to make sure they are getting to what they paid for. You. The product.
Well sure. If the requirements are stupid then they’re stupid. That’s not what you said before though. Showing content from the web doesn’t create stupid requirements.
I said “content from around the web”, in quotes. It’s what Microsoft calls this feature, that originated in Edge collections and spread like a plague over a bunch of UI elements.
It’s ok if you don’t know things. You don’t have to be a jackass about it.
I upvoted your reply until I got to your last sentence. I haven’t been rude. Why are you being rude? Meanwhile telling me not to be a jackass about it…
Some introspection might be in order.
I’m blocking you and moving on now.
Yes, a hodgepodge of shit is of course worse. But fucken say that then. Dont say, “its literally a react native application! Thats why its so bad!” when that is not true and sounds ignorant.
Personally, I am 100% grateful for this correction, because I didn’t know and since I’ve heard the less accurate ragebait version dozens of times at this point I would have been confused, next time I have to spin up a Win11 image, why I couldn’t replicate the spike I’ve heard so much about. The fact that it’s tied to a particular UI component, one of many that machine provisioning scripts and playbooks commonly disable, means it would have remained a bothersome unresolved mystery to me forever if not for your comment. So thanks.
Oh it still spikes without the recommendations lmao at least my work laptop was because I, too, have all the bullshit registry entries to make Start Menu usable and resource monitor was showing 10% spikes on average each time I opened the start menu. Wild.