floatboth

It's all the other shitcoins that are mined on GPUs.

Some support for WMR headsets is available in https://github.com/OpenHMD/OpenHMD but without 6DoF / inside-out controller tracking so far.

It's mostly just a shitty version of VRChat with people you don't like.

Yeah, sure, definitely FreeCAD. OpenCASCADE failing to make fillets, blocking the main thread with long operations and crashing the entire application is exactly what I always wanted to see in VR!

It's not necessarily impoverishing and depressing. It can be, especially if enforced from outside, but many people find satisfaction in minimalism and frugality.

Exactly… the projection that datacenters' demand for computing power won't be offset by silicon efficiency improvements is somewhat speculative; the projection that Bitcoin's demand for computing power won't be offset by silicon efficiency improvements is obvious and is by design of the fucking system.

> the jury is still out on whether the energy saved _running_ Rust code will offset the energy consumed _compiling_ it

Obviously depends on how much the compiled code is run. If it's a one-off script, no. If it's a server that will serve a million requests, or a browser that is shipped to a million users that will use the same version for a few months, a thousand times yes. And the vast majority of energy use that can be attributed to programs is in the second category.

…or clicking the On-Click Transitions in Microsoft® PowerPoint™…

This HDR obsession makes me want to abandon color entirely and switch to E-Ink.

Even worse: Bitcoin alone uses as much as the datacenter sector as a whole, not just Google.

rebase.autostash=true is also a thing, but the "working copy as commit" concept does look more interesting.

No, you won't see corruption on ZFS. Cutting power to the drive is always safe, you can slice a SATA cable with a guillotine if you want, you'll always see a consistent state of the filesystem. ZFS transactions are entirely atomic.

ZFS (and btrfs) is not "journaled", it's copy-on-write.

I use it exclusively, don't remember the last time I looked for the title bar.

How about desktops that don't have anywhere to put status icons? i.e. what if I don't want to have any panels? Working as a normal window should be an option in all applications.

A dedicated tray is a concept tied to windows 95 style UX. I hope the new designs are more about standardizing ways to indicate various statuses and actions of "the app" broadly, without dedicated status icons. For example download progress is still only an Ubuntu Unity protocol that KDE also supports because they can but it's all not freedesktop standard.

On the other hand (ha) it does not require any aiming. I can super+drag windows into "aero snap" targets in milliseconds because I don't have to spend any time on finding the header bar.

> not only across light/dark and accessibility modes but also future OS versions

When Apple makes a future OS versions they are expected to avoid breaking apps.

The comparison here would be not to future iOS versions, but to arbitrary jailbreak tweaks that overhaul the look system-wide. You're not ensuring that will look good with your app ;)

No one can deny you anything with FOSS. Go ahead, edit everything, just please don't complain to the developers that something broke because of that.

For mouse too, actually. I grew up with scroll wheel mice so I literally never had a reason to use a scrollbar to scroll.

GTK4 is supposed to "just" build with meson on Windows – yes, just with MSVC, not requiring any of the GNU toolchain type things: https://www.collabora.com/news-and-blog/blog/2021/04/29/buil...

If no one has yet wrapped this into a Rust crate, someone should…

heh, but with Apple "X" is not the letter "X" but the roman numeral ten. (Which is why you should pronounce Xcode as "ten-code" :D)

Because CompactFlash is one of the most overpriced things in the universe I guess?

I bought a couple for retro (IDE/PATA) laptops and paid ridiculous prices for just 32/64 GiB >_<

I love the idea of tinkering with iPods, but I'm really, really not going to actually carry a dedicated music player device. Going back from modern convenience to retro inconvenience just isn't practical to me.

Can't say I've seen that often, but there was a short period of time when Twitch refused to play on a FreeBSD user-agent. Spoofing as Linux or Windows worked. They did fix it.

How is Akamai dying? Isn't Akamai still the largest CDN around?

150 dpi definitely feels sufficient to me.

And honestly I prefer grayscale even on 90 dpi monitors sometimes.

This is amazing news! I've been wanting this since the Nexus 5X where I built a kernel with KVM and was disappointed to see the "kvm failed to become hypervisor" message in dmesg.

Template Haskell and Rust proc macros aren't similar to pervasive CTFE.

TH/procmacros just give you lexical tokens, you then parse them (typically adding a monstrous dependency on haskell-src-exts/syn) and emit AST.

The way D is designed, you don't need such a special facility because CTFE is everywhere. You can run normal functions at compile time. You can have compile-time "static if" and "static foreach" statements, and use various introspection calls (confusingly called "traits") in those.

Zig has similar "comptime" functionality. C++ now has "if constexpr" but not any of the introspection features.

I don't have that much experience (don't really have many use cases for FPGAs personally tbh) but:

Icestorm is for iCE40, Trellis is for ECP5 (which comes in variants up to 85k LUTs);

the flow is simple enough to do manually but there are things that make it one-click. This tutorial series https://youtube.com/playlist?list=PLEBQazB0HUyT1WmMONxRZn9Nm... uses one.

As for handling really big designs, I don't know.

> and some lattice chips

Lattice has been by far the favorite of the FOSS community, but there's been more news:

- https://github.com/YosysHQ/apicula has appeared for Gowin FPGAs found on e.g. Sipeed Tang Nano boards (very cheap on AliExpress) - a vendor called QuickLogic made SoCs that only use the FOSS toolchain for the FPGA part, out of the box: https://www.quicklogic.com/products/soc/eos-s3-microcontroll...