Valve seems to be substantially responsible for the mess that is Vulkan. They were one of its pioneers from what I heard when chatting with Vulkan people.
There's plenty of blame to go around, but if any one faction is responsible for the Vulkan mess it's the mobile GPU vendors and Khronos' willingness to compromise for their sake at every turn. Huge amounts of API surface was dedicated to accommodating limitations that only existed on mobile architectures, and earlier versions of Vulkan insisted on doing things the mobile way even if you knew your software was only ever going to run on desktop.
Thankfully later versions have added escape hatches which bypass much of that unnecessary bureaucracy, but it was grim for a while, and all that early API cruft is still there to confuse newcomers.
Which is very weird, considering mobile GPUs by their very nature use unified memory, so supporting things like bindless and GPU pointers (which in this case are just pointers) would be more straightforward than on PC, where basically you have 2 computers with separate memory spaces connected via PCI Express
Bindless has nothing to do with UMA and everything to do with the fundamentals of how your GPU accesses memory. Older GPUs had limited register spaces where they could store texture and buffer references, the hardware had no instructions to read textures or buffers outside of the references in those small set of hardware registers. They just weren't able to issue a request to the texture unit to read any old texture, it had to be in that set. The GPU itself wasn't able to update those registers, only the CPU could.
UMA or not doesn't matter, desktop GPUs have MMUs and are perfectly capable of reading the CPUs memory in a unified address space (even back then).
That would be interesting. I have long wished that Sony phones would allow re-locking the bootloader to an OS signed with my own keys.
Some of their Xperia Compact models have been excellent, but they haven't been making them like that in recent years. Dare I hope for a return of their truly compact flagship phones and GrapheneOS support?
As far as I'm aware, their flagship Xperia phones do support bootloader re-locking [1]. The problem is they haven't fulfilled GrapheneOS's other requirements: https://grapheneos.org/faq#future-devices
I use Sailfish on an Xperia 10 mod. III. Unfortunately the only Xperia models which support the full Sailfish w/Android compatibility are the way too long ones. I intensely dislike long phones. I miss my old Jolla phone (they're the maker of Sailfish), it was perfect but developed a technical problem after many years. The Xperia is clumsy when compared to the Jolla phone. Glass surfaces back and front (who thought that was a good idea? Glass is slippery, and glass breaks), sometimes slips from my hand, or wherever I put it if it's not 100% flat. Glass..well, you get the idea what happens then..
Search for "Local-only commands removal" on the page for the relevant section:
Local-only commands removal: We are removing known mechanisms for creating a local account in the Windows Setup experience (OOBE). While these mechanisms were often used to bypass Microsoft account setup, they also inadvertently skip critical setup screens, potentially causing users to exit OOBE with a device that is not fully configured for use. Users will need to complete OOBE with internet and a Microsoft account, to ensure device is setup correctly.
I wonder how much of this is Microsoft trying to create recurring profits from the base (Home) sku, rather than that they care about local-user installations in any other circumstance.
Because it seems that microsoft could not shitify windows experience anymore.
I like windows, Its a great system specially for being productive, but the godamn start menu using react and edge and the online requirements are a pain in the ass.
Sometimes it just hangs while you click the windows key. All I want is to open notepad++...
This is the story of Windows since 7 (and even earlier if you used the crappified Windows typically included with hardware): "The default experience is dogshit, but with enough work you can fix it." With every release the work required to make Windows bearable increases.
Microsoft to push pwa outlook as the default client also is terrible. Why would I want a e-amil client that occupies 3 times the memory of the default outlook client?
Sounds like more lies: you can still use autounattend.xml as far as I know. If they broke this it would break almost all the top corporate enterprise stuff
(same reason they still have network printer driver vulnerabilities because they refuse to fix old shit in the name of backward compatibility)
