It'll be a requirement for OEMs, not for consumers. OEMs already have a list of requirements they have to meet in order to sell Windows devices. For example, for the last several years it's been a requirement that OEMs include a TPM in devices.
Before we all grab our pitchforks, maybe we should take a moment and realize that this is a single review on Amazon that's lacking in important details. The headline here reads "Acer disables BIOS for laptops sold through Amazon", but the review mentions that they're able to get into the BIOS. They're only unable to change the boot order, which is a lot different from "disables BIOS". Furthermore, I don't entirely understand why the reviewer tried to get a refund from Acer when they purchased it from Amazon. I bet there's a non-nefarious explanation for the disabled setting that the reviewer saw. Sadly with a $1,530 cost, I don't expect anyone here to buy the laptop just for research purposes!
Ryzen 1000 chips have TPM. We don't know exactly what feature Microsoft wants that they don't have. They announced this morning that they're going to do more testing of Ryzen 1000 and Intel 7th gen chips during the preview in the hopes of officially supporting them.
> Unless you have a recent store-bought PC that has Secure Boot and TPM enabled out of the box, you probably aren’t going to be able to upgrade, even if your hardware is theoretically compatible.
The vast majority of Windows devices are "store bought". TPM 2.0 has been an OEM requirement from Microsoft for almost five years now, so the only people that need to worry about enabling it are people who built their own PC, as in the exact type of people that would know how to do so.
I think there's two reasons memory usage is lower. First, WebView2 is essentially just another tab in an already running browser process. If they're not pinning to a specific version of WebView2, they're reusing the host machine's copy of Edge, which I believe is always running now, so startup latency is reduced. I think their numbers don't include the memory usage of this "always on" instance, and only count the Teams-specific memory usage. Second, Microsoft has done a lot of under-the-hood work to reduce memory usage of Edge on Windows that hasn't made it upstream into Chromium, so I suspect that gives them an additional decrease in memory usage simply by switching from Chromium to Edge-Chromium.
I actually did something a bit similar[1], but with a Raspberry Pi 4, which has native composite out. I have it looping through Plex playlists of media that was originally released towards the end of the SD era (although most of it is high-quality HD rereleases that get naively cropped to 4:3 by VLC). I do also happen to have a Miyazaki playlist, but it starts at Nausicaä instead of The Castle of Cagliostro. I'd love to replace my cheap thrift store CRT with a nice PVM/BVM though!
I just went through the Exposure Notifications flow on Android, and selected a region where it's not currently available (Arkansas). It displayed a message saying it wasn't supported in my region, and left the setting disabled. While it's still possible that your theory is correct, I certainly don't think it's the intended flow as of now.
Virtually every non-trivial Android application has these permissions, none of which are even important enough for the system to prompt you for permission. The only interesting one is "pair with Bluetooth devices" which is how the Exposure Notifications system works.
I think it's far more interesting to think about what went wrong so that the MassNotify app actually displays as installed on these devices. All of the Android COVID exposure apps for US states are simply the Google Play Services COVID Exposure Notifications code with an icon, splash screen, and possibly some text. The idea is that you enable the setting by installing the app, but in this case it seems that rolling out the setting itself has caused the app to appear as installed. I wonder if there was a misconfiguration on the part of the MassNotify developer, which caused this. The push to devices enabling the setting is likely automatic on Google's end, so I doubt a human did a check to ensure the MassNotify app behaved as expected.
At the end of the day, there likely wasn't actually anything more than a package ID installed on user devices. It didn't opt anyone into exposure notifications, and it most likely didn't include any executable code.
I honestly don't envy Microsoft. On one hand, you have the people who don't want Microsoft to break backwards compatibility. They want Microsoft to retain the ability to run programs written a quarter of a century[1] ago. This is why all this legacy stuff sticks around in Windows. Then, you have those who want Microsoft to radically reinvent Windows, either by embracing WinUI 3 fully (what most people mean when they say UWP) or through something even newer. Windows 10X was a sort of middle ground: a OS that pushed all the old cruft into isolated containers. Sadly it looks like that approach isn't going anywhere (unless we see it come back in Windows 11). Project Reunion is a nice attempt to give developers an incremental upgrade path to modern Windows, so I'm hopeful that within the lifecycle of Windows 11 we'll start to see Microsoft develop a reasonable separation between modern and classic Windows apps.
[1] Edit: quarter of a century, not quarter of a decade.
That's a totally fair point, but the argument to that is "don't support this developer" not "sell your Oculus Quest". Getting mad at Oculus for this is basically like getting mad at Apple because developers are including ads in their paid apps.
I honestly don't understand the doom and gloom from this announcement, which essentially amounts to "leading VR platform tests new way for developers to monetize applications with personalized ad service". People seem to think this is Facebook injecting ads into games all willy nilly, when in fact it's just a platform for developers to add ads to their VR apps/games. If a developer can't make ends meet with a full up-front purchase price for their app/game, I'm totally supportive of them trying the ad-supported route. At the end of the day, I'm glad that Facebook/Oculus is giving developers access to this so that they can make their own choices regarding the monetization of their software.
This has been upgraded from "screenshots leak" to "he entire Windows 11 OS has appeared online". The reporter of the article has it running, and is sharing more details as they discover them.
As someone who was initially resistant to hooks, I actually find that they're a more expressive API to how I was already thinking about my applications. There's footguns for sure, just like there are with class components, but I found that rewriting my class components with hooks instead actually made the code cleaner and easier to reason about. That being said, it's possible the benefit simply came from the rewrite, but even with newer components, I feel like hooks are a better API.
I usually give Google shit for copying everything Apple does, but I sincerely hope that they (and Microsoft) copy this feature. I'd love to have extensions like Stylus and Microsoft Editor on my phone. Plus this would open up a massive audience of users, which would hopefully further inspire developers to build interesting and useful extensions.
This is certainly one of those instances where I'd raise hell, but I actually avoid trying to file lost item claims with Amazon for smaller ticket items. I know they have automated systems in place to prevent fraud, and I'm terrified that reporting for smaller ticket items will get my Amazon account banned. I've had a friend have this happen with his Doordash account; the sushi place he orders from a lot was pretty bad at sending everything he ordered, and after reporting this to Doordash every time, they eventually disabled his account. To this day, the restaurant is still on Doordash.
Qualcomm has released several ARM-powered Windows laptops, and just announced today a desktop-form-factor Windows Dev Kit powered by the new Snapdragon 7c platform.
OBS has a slight learning curve, but I find that it's able to do everything I need, including screen region recording, single window recording, and overlaying/switching between screen and webcam.
Oh my goodness. It's wonderful. This needs to be part of browsers by default! The only suggestion I have so far is it'd be pretty nice for it to be a tab in the dev tools, potentially with element highlighting as I hover over the nodes.
One interesting aspect of WebP support (or lack thereof) is that it doesn't work in Slack or Discord, even when those are running in a supported browser. I think things like this are inhibiting adoption of newer formats.
I love that there's a call for more UX patterns to be built into native elements, but I really wish there was a massive push to develop better a11y tooling for developers. Chromium has the A11y Tree View, but it's so noisy that as someone who isn't intimately familiar with the interaction pattern of screen readers, I can't easily digest where the issues are.
I'd love to see a purpose-built browser that "renders" your site purely by the a11y tree, but in a layout similar to how a site might look. That'd make it super easy to see missing buttons, links, uninteractable elements, etc. I'm sure there's efforts within browser developers to do this, but it's frustrating that most of the work is being spent just telling developers their sites are inaccessible rather than giving them the tooling to help make their sites accessible.
I'm a bit perplexed as to why cicadas have been in the news lately. It's my understanding that almost every year there's a brood that emerges. In fact, I think it's more noteworthy that 2023 will be the first year in almost a decade without the emergence of cicadas.