#On Screen Keyboard's Windows key has the old Windows 10 logo
37 messages · Page 1 of 1 (latest)
This would be a good meme, but as it's the #1 operating system used, it's just a sad truth.
it's because Windows 11 is reskinned Windows 10 with explorer.exe turned to an UWP app
in fact Windows 11 uses the exact Windows 10 kernel too (Windows NT 10.0)
they are the same
Windows 11 has just more UWP garbage
Fun fact, the new Explorer isn't a UWP, however Microsoft had planned a UWP version of the Explorer for the Anniversary Update. You can try it out by pressing Win+R and pasting the following path: explorer shell:AppsFolder\c5e2524a-ea46-4f67-841f-6a9465d9d515_cw5n1h2txyewy!App
Well windows 11 and 10 used the windows xp classic theme
This is a nonsensical statement. They are not the same, of course they share a big bunch of code, but version numbers are completely arbitrary and do not imply this in any way.
people are so ignorant about windows
if you're gonna hate then do it correctly
first the explorer is web-based now the explorer is uwp
ig this is due to that particular on screen keyboard being abandoned
this one has the new logo
but yeah i dont get the need to have two, maybe because accessibility options uses the older one?
still functions the same
no diff
What does this even mean? "Function the same"?
they do the exact same thing
all criticism I give on 11 is less taskbar customization
that's really it
spyware is both on 10 and 11
What kind of visible tangible difference do you expect between two different kernel versions?
uh none
there is no visible difference
Then do 10.0.10240 and 6.3.9600 also "do the exact same thing"?
no
How not?
10.0.22000 and 10.0.19041 are as much the "same kernel" as 10.0.10240 and 6.3.9600 are.
Just the fact that they both start with 10.0 doesn't mean anything on its own.
Version numbers don't follow some law or rule, they are entirely arbitrary constructs.
Just like Windows 10 started as 6.4 and then turned into 10.0 mid-development. It's not like they made a huge leap that justified a huge jump in number. It was a decision made for non-technical reasons.
And likewise, MS could have bumped the number for 11 to 11.0 or 10.1 or whatever, but they chose not to bother with it.
And just like the build number always makes a jump forward with a new development semester. Some person says "let's jump by 500" and then it's done, and the build that jumps by 500 doesn't have more changes than the previous build that jumped only by 1.
And I was about to say that the only thing you can derive from two build numbers is that the higher number is that of a newer build. But not even that is true. Windows has concurrent development branches and often, a lower build number is newer than a higher one. Case in point, Beta vs Dev vs Canary.