Recent observations from users on the social platform X have uncovered performance issues tied to the Windows 11 Start Menu, revealing that the component
What in tar nation? Why would they ever do such a thing? The main point of React Native is to make an application cross-platform (i.e., so it can run on multiple operating systems). What’s the point in developing a Windows Start menu that can run on macOS, Android, or whatever?
Unless they’re going for the second point of React Native, which is to be able to develop with JavaScript, which has an abundance of developers (i.e., it’s less expensive). Maybe they thought that this was the main point, regardless of performance issues.
If I were to venture a guess, it’s so that they can use the same start menu in multiple iterations of windows without tinkering (so, for example, they could dump a windows environment onto an xbox as an app). Kind of an ass backwards way of doing so in my opinion, but that’s on-brand for modern microsoft
At a higher level, as in multiple operating systems. I think it’s probably high enough that it doesn’t care much about the hardware platform as long as it’s supported. But I don’t know the technical details of developing with React Native.
Also, you probably didn’t read my whole post. The point I was making was that the primary reason to use React Native is for cross-platform development, THEREFORE it makes no sense to use it for the Windows start menu because what would be the point of porting that to another OS?
What in tar nation? Why would they ever do such a thing? The main point of React Native is to make an application cross-platform (i.e., so it can run on multiple operating systems). What’s the point in developing a Windows Start menu that can run on macOS, Android, or whatever?
Unless they’re going for the second point of React Native, which is to be able to develop with JavaScript, which has an abundance of developers (i.e., it’s less expensive). Maybe they thought that this was the main point, regardless of performance issues.
If I were to venture a guess, it’s so that they can use the same start menu in multiple iterations of windows without tinkering (so, for example, they could dump a windows environment onto an xbox as an app). Kind of an ass backwards way of doing so in my opinion, but that’s on-brand for modern microsoft
That makes a bit more sense.
Cross platform you say? So…like…ARM? 🙂
At a higher level, as in multiple operating systems. I think it’s probably high enough that it doesn’t care much about the hardware platform as long as it’s supported. But I don’t know the technical details of developing with React Native.
Hmm I wonder why…
Oh so you know? Why are you wondering then?
Unnecessarily biting reply. Microsoft investor perhaps?
What a strange thing to say lol.
I was pointing out that you asked why they would do something while answering why they would do something straight after.
Your post came across pretty harsh.
Also, you probably didn’t read my whole post. The point I was making was that the primary reason to use React Native is for cross-platform development, THEREFORE it makes no sense to use it for the Windows start menu because what would be the point of porting that to another OS?
To use it on other OS’s, like Android.
Windows start menu in Android?
Yep, just a matter of time if you’ve been paying attention. They’ve given up on Windows mobile, but not on Windows on mobile phones.
Ok, that doesn’t make sense to me, but Microsoft is pretty aimless these days so I won’t say it’s impossible.