He's at fault for keeping them in place, but that's about it.

Yeah, I assume you mean the manual refresh button that has gone missing? Pisses me off too when I know there is new mail.

You can click "Inbox" again to force a refresh. Still sucks, but better than reloading the entire page forcibly.

NixOS is great, but if someone pulls the repos for the source packages of somethings in NixOS... you're just completely out of luck.

But if you know the hash, and someone in IPFS still has it available....

In fact, that's behind: strong memory safety, Option/no-null (probably lumps in with "strong memory safety") and of course generics and the type system at large.

The speed is honestly a nice benefit. (I'm not being sassy, I don't have speed intensive applications and still reach for Rust).

There's a new CLI tool and dbus api for discovering and installing firmware updates that are securely hosted by redhat. There is also native support in GNOME Software for surfacing the updates and making them available.

This means on a Dell server, you literally type: `fwupdmgr update` and all possible firmware is updated.

So literally every comment in the thread so far is missing the point. This doesn't require shelling in, putting it in the UEFI partition, orchestrating your infrastructure to reboot the servers into the EFI partition to install and then let it reboot back to Linux. You just type `fwupdmgr update`.

But mostly I remember complaining to my dad. QBasic "compiled" to some intermediate that required QBasic to run... I remember never being happy with that.

I thought I had eventually found out... but QB64 only supports XP, and I know that I was doing QBasic on something much older than that... Maybe older versions of QB64 supported earlier versions of Windows.

anyway, a nice little 5 minute trip down memory lane.

And with the Razer Blade + Core set to actually make eGPUs a big thing... I'm pretty disappointed. I'll probably end up with a Razer Blade sooner rather than later.

Given who I'm replying to, I'm assuming that I'm missing some key piece of the puzzle.

(And I totally acknowledge it doesn't change the circumstances of what either side has done, I'm just curious)

Oh really? What else are you supposed to do when a startup flush with cash decides to ignore the laws of your nation, exactly?

It's kind of weird actually. There's two sorts of people that defend these announcements, I've found:

The first thinks that they are going to build an "amazing" platform some day and that they'll follow this model for "growing revenue". So of course they defend it.

And then there's the second group that has some "great idea" who plans to build on Slack's platform. Personally, I look forward to 2 years of stories about how Slack was unfair to them, or changed the rules on them, or broke an API. Or didn't review fast enough, or any of the other complaints that pop up monthly about other closed platforms.

Whatever the convergence plan is, Pixel C is the test hardware. The bootloader bits are in the ChromeOS tree. It uses Coreboot.

It's a ChromeOS device and I suspect it's future will include a return to its roots.

ARC in Chrome will be a better way forward for Android than trying to fix all of Android's insidious problems on the "desktop" and making mobile Chrome more fully featured. It just seems painfully obvious that Chrome is going to win.

It's better tech all around.

Tears of joy stream down my face.

It's just painfully stupid in every way. If it was a built in extension that by-default talked to a Mozilla hosted open source Pocket clone, we might be having a different conversation.... but I'd still be annoyed.

Just as annoyed as I am that Chromium (yes, Chromium, not Chrome) comes with a god damn Google Docs extension.

Though, I've never, ever had a perf problem with it.