I use side tabs because I'm trying to maximize horizontal space on a wide laptop screen. The widescreen standard leaves a lot of unused space on the edges. I could zoom browser text to go edge-to-edge, but then it's unnaturally large font and I get only a few lines of reading before I have to scroll. Making text/docs/webpages fill the center 2/3 of the screen is comfortable for me, leaving the outer 1/6th on each edge perfect spots for tabs.

I don't know why I should care about limited compatibility for a subset of devices with another subset of devices. There's some of everything in my home. I found a tool called LocalSend years ago that allows me to do mildly obnoxious data transfers between arbitrary devices regardless of platform.

... and Figure 3

If you start messing with the accessibility options for text size on MacOS, you quickly wind up with a blurry mess. This is particularly obnoxious if you're looking at a very high resolution display and very noticeable on the menu bar. It's a wonderful example of Apple's one size fits some design priorities.

MacOS is a third-rate *nix that can run MS Office, but so is ChromeOS. Should I be excited that I suddenly have the option to run Photoshop on a $600 device with as much RAM as the phone I had in 2018, but still can't control the size of system fonts on the desktop? Or is it just a more expensive way to run a browser and an SSH to something I'd rather be using?

I'll give you a hint: It's the second one.

If they're being thorough, Snapdragon, Mediatek and Ampere (server) SoCs are also being sold in traditional PC forms.

I might be interested if this thing could run Linux and had Thinkpad-grade input devices, but as it is, it's just a web terminal that's locked to Apple's ecosystem instead of Google's. That's just not very compelling.

What big European player wants to put $6B on the table though? SAP is the biggest European software company I can name and that doesn't seem like a strategic fit to me.

Western governments have always downplayed these kind of incidents.

It's about time we face reality.

https://www.redlabel.ltd/intel...

Agreed, especially with the fact that titles will randomly disappear based upon what the service feels like paying a license for. This results in seemingly popular movies just not being available, which keeps surprising us. Case in point, we wanted to watch the DiCaprio/Danes Romeo and Juliet, and it wasn't available on any streaming service except to "rent" for $4.99. We found the dvd in the basement and watched it instead.

I miss going to blockbuster with my girlfriend and wandering around, looking at what's newly released, debating what we wanted to watch, and getting that tub-o-microwave popcorn. It's somehow easier and more fun than scrolling through menus in an app.

Used to take several minutes in the nineties.

This has been around for quite some time.

This article on related research in Belgium is from 2012.

https://wavewatching.net/2012/...

And they are now building a commercial scale facility.

https://www.sckcen.be/en/infra...

Everything new enough to use DDR5 has the DRAM controller embedded in the CPU, so we'd be talking about something more than just new motherboards.

I spent about 3 weeks trying to get 4x64GB DDR5 6400 working on an AM5 workstation. I never got it to run for more than about six hours at anything faster than 4200MHz, no matter how much I fiddled with timings and voltages.

Hilariously, that spare 128GB RAM kit is worth like $2000 right now.

Consumer DDR5 platforms have a hard time using more than a pair of DDR5 modules at any but the slowest timing and currently don't support DIMMs larger than 64GB. Workstation and Server Platforms can already support more RAM than that, but if you're buying a new enough Threadripper, Epyc, Xeon or Ampere platform to handle DDR5, you're almost certainly buying it with rDIMMs in the first place.

Check back in five or six years. I'm kind of serious. I just pulled my oldest 7.6TB u.2s at the end of a three year service term, drives I thought were unimaginably huge when I deployed them. When I checked them, I found that they had around 70% estimated wear life remaining, which seems pretty good for drives that were in use constantly for so long. The replacement drives were 15TB each, and I expect that in another three years, I'll be ready to fork over for the 30TB ones.

I'm thinking this is pretty typical for drive deployment life cycles.

28GB/s under conditions that will never be met for more than a few seconds at a time given most enterprise workloads isn't nearly as interesting as getting 200k IOPS+ sustained random reads for arbitrary lengths of time, and that's something that's theoretically possible even on PCIe gen 3, albeit not on any drives that currently exist.