Task Manager's expanded view does include GPU monitoring and has done for quite some time now, but it wasn't added until they achieved a certain level of market ubiquity (and, presumably, the relevant APIs were in place). I'm guessing that Microsoft now feels that NPUs have reached a similar state and will be adding the extra "NPU" sub-tab to the existing Performance tab where other hardware resources are monitored, and adding some additional AI-related monitoring functionality to the existing GPU one.

You don't have to use it (SysInternal's tools are much more comprehensive), but if you just need an overview level of insight into what is going on when your system's fans start to sound like a jet turbine, it's still a pretty good starting point into what's up.

Unfortunately, refundable tickets are more expensive.

In Soviet Russia, Amazon sell book to you!

I suspect the Pareto Principle is very much at play here, in that 80% of customer issues can totally be answered by the scripts that human front-line call centre staff typically worked from (that's why the scripts exist in the first place, afterall), and therefore 80% of the calls can be dealt with perfectly well by an AI bot following the same script. It's only the other 20% that are the unique problems that KB articles and scripted/automated agents cannot handle, and - usually after a lot of pointless tick-boxing to get off-script - those are usually the ones that get escalated to a second line support peon that can actually take some initiative, and ultimately the few real corner cases to third-line support.

If AI can let you cull 80% of your support / call centre staff with no practical loss of service (according to the AI agent salesperson, anyway), then who isn't going to jump at that? Of course, they'll probably go for 90% or more and take extra hit on service levels, then have to wind things back a bit when they realise that the AI agents are not quite as good as promised and some people will get really stroppy about being forced to talk a bot, but at that point they'll have been paid their bonus and who cares, right? They're only customers, and you've got think of the shareholders!

Brain and brain, what is brain?! By 17 years old you're expected to have seen The Empire Strikes Back and have committed "R2-D2, you know better than to trust a strange computer" to your memory.

...requires age verification on traffic coming from known VPN addresses

A state enacting such a law should be required to publish their official list of The Known VPN Addresses.

People running websites should not be required to make up that data, or have to pay to subscribe to someone else who makes it up. If the gummint wants to force something that ridiculous on us, the gummint should make the taxpayers, not the webmasters or their users, pay for it.

Which is why, as many people pointed out at the time the root servers were opened up to all these new gTLDs, that this is just a license for the successful registrars running each gTLD to print money at the expense of everyone with a brand they have to protect. In most cases, they were absolutely right on the money; .biz being the classic example, almost immediately becoming a wretched hive of online scum and villainy most mail server operators equally rapidly blocked outright. (I am curious though; does anyone actually try and host a legit .biz domain these days? I don't think I've ever come across one.)

I'll give you, there are some pretty cool options for host/domain names under .web, especially with an arachnid theme or things like "web.web.web", that might become useful and popular for some groups, but apart from those - which Verisign, being Verisign, will no doubt have a special procurement process for to maximise their investment - the rest will almost certainly be parked/redirected brandname protection, a vast number of of scammer sites, and a handful of vanity projects that 99.99% of people probably won't even know about, and probably wouldn't care about if they did.

None of which changes the fundamental point that we seldom care about URLs any more. We click on links in apps, webpages, emails, etc., ideally having done some kind of due diligence to make sure the link is hopefully OK, or just cut and paste from the browser bar to put it into something we are writing. Functionally, "bankofamerica.com" is no different from "bankofamerica.web", or any other gTLD/ccTLD they might care to suffix it with, and it wouldn't make any difference to their service if all the other TLDs went away, unless they wanted to do some kind of content localisation based on a ccTLD rather than some other approach to achieve that.

Sam Altman is also a psychotic sociopath. He's probably pitching "Project Skynet" to Trump and Pete Hegseth right now - "Look how effective our tools clearly are! You could be using them against China, Iran, Cuba ..." [checks notes] "Um, Greenland, Canada, Democrats (especially Obama & Biden!), E. Jean Carroll, the BBC... And for the low, low price of..." [pinky finger] "one trillion dollars, we can be up and running by, let's say... 2029?"

It's been a while, but I've written some Fortran 77. I changed the value of 4 long ago. Sorry, everyone.

It's irreversible in that it's a pain in the ass, so they would prefer to not help.

It's reversible in that other forces (e.g. negative publicity) can be greater than the pain in the ass.

her expecting me to read her mind and magically know how to please her in every way, (a very long list), was always a factor.

oh, so by dating you mean watched 80's comedians all day . got it.

No, it means there are communication problems, which is far more common and cliche than even 1980s comedians.

It's bad, but Microsoft has a awfully large number of lines of code to run through Mythos or whatever (whether they need that many is a whole other discussion). A more useful metric on overall code quality would be how many bugs are being found per 10k lines of code compared to their peers (including FLOSS); e.g. if Microsoft ran 10m SLOC through Mythos to get those 570 bugs, and a smaller project ran 1m SLOC and got 57 bugs, then you could reasonably argue that their code quality is about on a par with the smaller project. It's still Apples to Oranges though, because some coding solutions are going to be much more challenging to code, and therefore more likely to contain bugs.

On the upside, we're probably going to get several months of this while everyone with access to Mythos et al runs their existing code through it and integrates into their release processes for new code, and the end result will be things being much harder for all the bad actors in the world. Even if you don't use the improved code yourself, that's hopefully going to have a significant impact on the number and size of all the botnets out there, and that's a net benefit to everyone apart from the bad actors.

Not getting any sunlight until past 10.00 AM is so annoying,

Well not getting any sun past 4:30 in the afternoon is also so annoying.

Gosh, it's almost as though people in different geographic areas have different needs and desires. If I didn't know HOW IMPORTANT it is that we all be forced to do everything the same, I would suggest that timezones be regional, agreed upon by local governments. But of course that's heresy since not every local government would make the exact same choices.

If the governor wants New Yorkers to be able to get cheap RAM at AI bankruptcy auctions, shouldn't they build the datacenters now?

If you wait a year to give permission, the bubble will have popped long before any hardware ever gets shipped, so the bankruptcy auction won't have anything to sell.

A rust-bearded robot driver sits on a barstool, sipping nonalcoholic syntha-fuel. "They're replacing me with a human!"