… Hydrogen cyanide is literally what has been used to execute people in gas chambers and genocide during the Holocaust. The LC(Lo), the lowest recorded lethal concentration is 107ppm, resulting in death in 10 minutes. That’s, objectively, far more dangerous than the respective material that firefighters were exposed to at Chernobyl. You don’t want that in any appreciable quantity in the air around people that you want to continue living.

And if you have a 3D printer, you can make your own pieces and share them with others.

I really wish that an affordable desktop chip fab was a thing. Maybe with graphene semiconductors it could be feasible.

Curious from your perspective what you’d like to see. From mine, Viture and Xreal are nearly perfect, with the exception of Xreal failing to be supportive of open APIs.

That’s what they were SO close to getting. Solutions like Xreal Air and Viture are just much more comfortable and less isolating.

Indeed. I think that my questioning was more rhetorical but explicitly spelling it out can be helpful.

This is true. However, the things that has me excited is that, since they are SiFive cores, they should be fully compliant with the RISC-V spec (as of the HW implementation). Other recent Linux-capable RISC-V chips, such as the T-Head C910 have been non-compliant, either due to being released before extension acceptance (Vector extension want at 1.0 before they shipped the design) or hardware design bug (floating point module does not raise underflow exceptions, causing violation of IEEE754, and non-compliance with the RISC-V spec). Issues like these have caused them to be blocked for mainline kernel support (implementing support for non-compliant chips breaks support for compliant chips or requires support of a “sub-arch”).

Nonetheless, I hope this does well and helps drive improved support for newer and faster RV64 chips.

The state of Michigan has no historical connection to the AR-15, to my knowledge. Why don’t they pick something that is actually native to Michigan like the Johnston Muzzleloader?

!!! And they’re SiFive cores!!! This is awesome.

That’s not to say bikes don’t have any safety at all… there is R&D that goes into making them safe in a collision… as safe as they can be.

Yup. I survived a high-side collision after being sideswiped by an SUV. Thanks to modern safety gear, I only had minor injuries with little long-term beyond an ankle to lets me sense slight changes in atmospheric pressure.

Extra bonus: Odyssey was supposed to feature a female lead, rather than the choice, but a misogynistic Ubisoft exec vetoed it, which I can only assume was reason for the absolutely garbage dialog.

Don’t know that they’ll all be ported to PC but the Supermassive standalones (Until Dawn, The Quarry) and Dark Pictures Anthology are great, if you like horror movies. I prefer to watch my wife play them. They’re literally like interactive/choose your own adventure films.

I have a first gen pair of Airs that I absolutely love, except for the lack of open-ness. I think that I’ll have to try dumping the firmware and writing my own at some point - likely when I have to replace the frames (have had to CA glue and tape the right arm three times now; I’m rough on my electronics). The teardowns that I’ve seen show that they contain almost entirely common off-the-shelf components (MCU, IMU, I/O expander, etc), so, shouldn’t be too bad to implement via Arduino or Rust.

The thing that drives me most crazy though is the lack of forethought on the Beam. It does it’s job great but they didn’t bother to have a dedicated power-in or support high enough wattage to run it off of external power. It’s absolutely maddening to have to recharge it 3/4 of the way through work. Think I’ll be modifying it to add a USB-PD input for power.

Here’s some extra fun: there’s a decent chance that you only need a cable with JST or DuPont connectors. I’ve seen a fair number of laptop motherboards with unused SPI headers/connectors just hanging out. My understanding being that they’re for possible accessories or, literally for flashing/debugging the bios.

For me, I think it’s just not ready for non-Debian distros yet. The docs and packages just aren’t up to parity. I like a lot about Incus and its general direction but libvirt and virt-manager are fully functional at the moment. Passing through devices with virt-manager is dead easy.

I’m still getting things set for Silverblue to be my baremetal hypervisor distro on my laptop. And by that, I mean giving up on Incus, setting up libvirt, and… everything is working like it should. I wasn’t expecting that. Now, I’ve got to find something else to do with my time.

Apparently, Viture has been much more FOSS friendly. Xreal really wants people in their ecosystem and have as of yet refused to provide documentation or open API, though there’s been a good deal of success with reverse engineering.

To add to this Ardour may be worth a look for DAW. I haven’t touched it in a while but recall it being rather nice.

Almost definitely.

I just wanted to offer some nuance to the table. After everything has been learned, enabling some (otherwise complex and obscure) features can be accomplished by a single line in your NixOS config. Like, this efficiency can not and should not be ignored.

I really appreciate it. I really WANT to like NixOS. The level of efficiency and portability (ex. Nix as package manager) is incredible and, I think, well worth learning about both for users and distros - I hope we see the ideas propagate further. It’s just not in a place that I can be happy using it. But, it is going to tickle some people the right way and that is something that makes me happy.

Fedora Atomic does deliver on those without requiring you to go into the deep and learn an entire new language that’s only used for managing your distro 😅.

This right here is why I’m liking it so far. I’m like Alton Brown is to cooking gadgets when it comes to languages in computing, I really don’t like unitaskers. I get unreasonably resentful of software that forces me to use a DSL (this is a “me” problem).

Does it require you to climb through heaps of trash documentation? Absolutely.

That’s why I think the previous commenter’s statement rings true. I’ve been using Linux exclusively for over a decade across multiple distros. NixOS is not intuitive for new or seasoned users, making good documentation vital.

An example: I spent a good weekend day or so poking at NixOS. Live boot worked as expected. When I finished, I had a bootable system but no network stack, despite following the docs. This means that my only route forward would be going back to the live boot since there was no way to pull packages in that state.

I decided to go with Fedora Silverblue as my next test. After dding the image to my USB, it took about 10 mins to get up and running. I was able to setup libvirt and other similar software quick and easy. And once I’m happy, I can write my config to a repo and have my base system wherever, whenever.