Dang, I had no idea and never thought to inspect it; thank you for pointing that out, now maybe I can finally figure out how to nicely shutdown from the terminal

The concern for code duplication is valid, but as the article mentioned it is also a while off until the Nova project is mainlined. I honestly never thought of how the work to bring in Rust to mainline may in effect lead to a more complete deprecation of older hardware as we start to change API’s older/unmaintained components aren’t updated. On the flip side, trimming out older stuff might save maintainer work going forward.

What I mean with shutdown, is the flags have changed (So, I can’t do ‘shutdown -hP’ or ‘shutdown -hP now’)

I had no idea on the manual version tag, I’ve probably been using an old one for a while… Thanks for pointing that out.

Ya, when it comes to modifying a Guix config, I haven’t gotten used to all the guile commands and different system names that guix uses, maybe eventually I’ll learn the semantics.

I miss ‘systemctl poweroff’ (haven’t learned the new herd equivalent); also, ‘herd --help’ doesn’t really give any useful information and only lists a few things you can do… Have to really dig into the documentation (someday). Also, the ‘shutdown’ syntax has changed… Otherwise, most stuff has gone well

Ya, this (if active) looks like it would be a more approachable version of Guix for many folks

Kinda cool, I like the config generator; too bad there isn’t a sway or hyperland one so that I can copy it for my system.

Honestly, pretty effective, I used to balance the mattresses on my head when working in a dorm. Many societies used this approach to move things, and with three of them the have the definition of a geometric plane.

They could then potentially end up spending more time testing every possible combination of input then they would spending compiling with a strongly typed language that prevents the invalid syntax from compiling to begin with…

Honestly, this is maybe the most telling about where OP is coming from… If not straight up flame baiting; that or they mistook /r/rustcirclejerk as a serious subreddit

The constraint on memory isn’t on the compiler it is in the available ram and flash on ultra-lowcost/power microcontrollers, use can find some with less than 1KByte of ram, so that 32bit int could have been 4 8bit ints in your electric toothbrush. The packing of bits is space effecient, but not compute effecient and takes several extra clock cycles to finish when run on an 8bit microcontroller. It’s better to store it in the native 8bit word size for these devices. Further more, on more powerful systems using the smaller size can allow you to optimize for SIMD instructions and actually do multiple operations per clock beyond what you could do with the 32bit size.

There are reasons for these types to exist; as was mentioned elsewhere, if you don’t care you can always just use i32 or i64 for your code and be done with it.

I think this is a strong case for being ‘overemployed’; sorry I couldn’t make the drive (while doing my other/actual job)

This is so true, heck I’ve even ‘baked’ some custom PCB boards in the oven to do some cheap reflow… Every man belongs in the kitchen, that’s where all the big boy tools are

I have no idea how it works, but I always found tractor beams to be fascinating. I wonder just how far it can be scaled up to?

And this is why we can’t have nice things; it sounds terrible, but there should be a limit for how responsible we as a society need to be for the actions of individuals.

Not just this, most (?all?) browsers now support viewing standard PDF documents… So, they shouldn’t even need to installing anything as long as they aren’t using IE…

I believe Mozilla was heavily involved with the creation of Rust, although that has now been transitioned to the Rust Foundation; not sure if that impacts them and/or what other projects they might have

That and a rotating menu likely adds overhead costs as it prevents you from specializing (skills, equipment, and ingredients acquisition)

Rust’s cargo is great, I’d say it would be best to make the switch sooner rather than later once your code base is established. The build system and tooling alone is a great reason to switch

Honestly executives and board members who receive performance bonuses and golden parachutes should carry extra liability, such that these perks can be denied or even clawed back (and used to help the damages) when their decisions have these sort of outcomes. Nothing wrong with making more when things go well, but if you’re going to take a larger piece of the pie, then you need to be prepared to take a smaller piece when things go wrong (aka, cut executive pay before layoffs, etc.).