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.
To the user and in function, there’s very little difference between “It’s React” and “It loads a React submodule every time you use it.” The result is the same. Your first response is fair and informational. This one is pedantic.
Thats great, we are not normal users here and I can call that out. No idea what’s up with this encouraged ignorance just because its a Microslop product.
Pal… you’re acting pretty ignorant to my comment right now. OP agreed with you, said it was interesting, and said it was worth clowning them. You got petty. You put words in their mouth.
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.
I agree on that point, although KDE has it’s own issues - currently it complains that my graphics drivers aren’t installed correctly for widgets, while being able to game and use CUDA without any trouble at the same time lol
Edit: anyone having this issue should go into “System Settings” - “Plasma Renderer” and just try to set it back to Vulkan or OpenGL. My issues started with switching from the stable 595 NVidia driver to the 610 beta.
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.
To the user and in function, there’s very little difference between “It’s React” and “It loads a React submodule every time you use it.” The result is the same. Your first response is fair and informational. This one is pedantic.
Thats great, we are not normal users here and I can call that out. No idea what’s up with this encouraged ignorance just because its a Microslop product.
Pal… you’re acting pretty ignorant to my comment right now. OP agreed with you, said it was interesting, and said it was worth clowning them. You got petty. You put words in their mouth.
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.
If we’re thinking of end states, nobody should be using Windows anyway lol KDE would never do this to us.
I agree on that point, although KDE has it’s own issues - currently it complains that my graphics drivers aren’t installed correctly for widgets, while being able to game and use CUDA without any trouble at the same time lol
Edit: anyone having this issue should go into “System Settings” - “Plasma Renderer” and just try to set it back to Vulkan or OpenGL. My issues started with switching from the stable 595 NVidia driver to the 610 beta.
Found the React fanboi 😂
Truth fanboi but k
Of course.