No, all output from a remote PSSession is converted to XML and sent to the local shell. It’s only if you’re running PowerShell locally that it returns proper objects. It’s not a deal breaker, but it sure is annoying.

PowerShell and it's objects are awesome ... until they aren't.
One issue I face is that I use PowerShell to manage things on Office 365 / Azure AD that I can't do through the web interface. This is mostly good, except when it's not.

An example, if you're running something like Get-MailboxFolderStatistics on a local Exchange server, the statistics you get back are proper objects, and you can do things like sort them by size.
If, however, your run this against Office 365, you get output back that looks the same, except it's serialised as xml, sent down the line, and then deserialised for display. There's no option to tell it to return sizes in bytes, because you don't need to because it's an object and you can display it however you want. It then returns human-readable sizes (e.g. 12.3 GB, 486 MB etc) and now you can't sort it because it comes back down the line as text. If you want mailbox folders, on Office 365, sorted by size, you then need to grab this text, and parse it to turn it back into bytes, sort it, and then parse it again to turn it back into human readable text.

So you then need to do something like:
Get-MailboxFolderStatistics username | sort-object @{ Expression = {$tmp = $_.FolderSize -replace ".*\((.+) bytes\)","`$1"; [int]$foldersize = $tmp -replace ",",""; $foldersize }; Ascending=$false } | ft Identity,FolderSize

Solaris was never intended to be an alternative to Windows. Solaris on x86 was a viable to Linux once upon a time, but Solaris on SPARC was where Sun had their sights set, and it was a formidable combination with rock-solid hardware and a powerful operating system that enabled things we can only dream about on the desktop or commodity server space - think about things like hot swap CPUs and RAM, this is possible on Solaris SPARC.
Interestingly enough, Apple built DTrace into Mac OS X. It's utility is somewhat limited these days with System Integrity Protection (SIP aka rootless) but it's still there and can be used without disabling SIP if you're only tracing non-Apple binaries.

And the answer is no. Who in their right mind would use this, knowing that the moment Oracle's lawyers smell the hint of money in the water, they will change the licensing requirements again so that what was once free is now an expensive licence. They have form in this regard, they have done it before, and you're crazy if you don't think they'll do it again.

Once upon a time, Solaris was a solid alternative to Linux on commodity x86 hardware. Today? Not so much. The only reason to use Solaris is if you're in bed with Oracle, and the only people in bed with Oracle are people with money to burn.

Sonos is not supposed to be really simple, it's supposed to be a multi-room, wireless audio system with decent sound and an app controller that allows access to your own music library as well as popular streaming services.
If you want really simple, you'll get a stereo amplifier, a pair of speakers and whatever audio source you want, and you'll listen to it in one room.
If you want convenience, and audio synchronised across different rooms, then that's where Sonos enters the picture. It's not cheap and it's technically very sophisticated. They have good audio engineering driving the sound and, most importantly for me, they give you years of ongoing support without needing to keep paying for a subscription.

There are many other subwoofers that use the same general design as the Sonos Sub. It's notable however that the tech in the Sub (two opposed drivers working in opposition to cancel out the vibrations of the other one) is vaguely similar to this tech that Sonos have purchased.

This is an interesting development as Sonos already use a similar concept in their compact Sub.
They have two drivers facing each other across the central hole in the sub, firing in opposition to each other.
https://www.sonos.com/en-au/sh...
This cancels out vibrations in the cabinet and increases the displacement over a single driver.

I can't remember there being an option for my 286 to display more than 2556 colours, but for my 386, there was.
I had a Tseng Labs VGA card, and there was a plug-in highcolour DAC available that gave it either 15/16-bit highcolour (32k or 64k colours) or 24-bit (17M colours) truecolour.

I also remember in the 286 days that JPEG (and JFIF) images were uploaded to bulletin boards, but you had to first download them to disk and then run JPEG2GIF to convert them to a 256 colour GIF that the computer could actually display. Many JPEG images were actually created by GIF2JPEG, so although the format was capable of 24-bit colour, a lot of images were simply converted from 8-bit colour.

This could be a great idea, if they restrict the display of ads to unregistered/unlicensed versions of Windows.
If you have a full, legit product key or hardware entitlement, then no ads.
If you're running an unregistered version of Windows, then ads for you!

AFAIK, your passwords in Keychain are one of the few things in iCloud that are E2EE, and Apple doesn't keep the key.

NewEgg state on their website "30-day hassle-free returns". Many online storefronts have a similar policy.
NewEgg specifically say that you can return an item sold with the 30-day hassle-free return badge at any stage within 30 days, with no restocking fees and free return shipping.
It doesn't matter if the dude from Gamers Nexus intended to use the product or not, NewEgg sold it under the condition that it could be returned for a refund in full at any time within 30 days.

Why indeed? Because NewEgg promised that they would.

What, they want to put porn on the internet now? Nah, that'll never take off.

Google are straying further and further from their don't be evil mantra, and trying to take over the free web by pushing Chrome, that they are truly the new Microsoft.

Curiously enough, Microsoft are now the new Google.

Sure, you have to pay for Office 365 email hosting, but it's very, very good. It works better with regular email clients (unlike Google's way they map labels to IMAP folders) and it all just works.

You can mix and match licences, so you may only need one account with a Business Standard licence (giving you 50 GB of email hosting, plus the Office apps) and the other accounts may only need a Business Basic licence instead.

The spam filtering on Office 365 is excellent, and you can easily archive old users as Shared Mailboxes (each with their own 50 GB quota) for free, unlike Google where you have to keep paying for any mailbox you want to keep.

Anyone capable of designing or building a portable atomic or optical clock will be well aware of what relativity and gravity does to timekeeping and will take that into account.

Kernel Extensions (kexts) were deprecated in macOS Catalina, released in October 2019. They then transitioned to unsupported in macOS Big Sur, released in November 2020.

Now, this breaking functionality in Dropbox is not what it seems on the surface.
I don't know what is actually changing behind the scenes, but the outcome is that Smart Sync (which is what Dropbox calls syncing cloud-only files to the local disk, on demand) is still working if you double-click on a file in the Finder. It's only when you try to open an online-only file in an app (via File > Open) that it won't sync.

So, it's not that this functionality is completely broken, but it's more likely got something to do with securing the way that kexts can communicate with third-party apps.

If you commonly double-click on files in the Finder to open them in third-party apps, then you'll likely notice nothing amiss. It's only if you were to then be in an app, and go to open a file directly that it will fail to sync, and only if it's an online-only file. Syncing of files that are synced locally to the Mac will continue to work as expected.

The API in question is already deprecated, and has been for quite some time. Microsoft and Dropbox have known about this change for more than a year and haven't taken the time to update their software.

Apple are now finally removing the API altogether (as they always planned to do), and that's what is going to break Dropbox and OneDrive syncing.

Dropbox have not even updated their software for native Apple Silicon support on Macs, when the hardware has been available to developers since June 2020. I'm not at all surprised that they have also not updated their app to not rely on a deprecated kernel extension...