It floors me just how many people in this thread feel like analog clock reading is a useless/outdated skill.
But I’m of the opinion that there’s no such thing as a truly outdated and useless skill, so I’m not sure I have the capability to empathize with those people…
You can use nix alongside guix, it’ll just double-up the dependencies on disk:
services (append (list (service nix-service-type))
%base-services)))
Services are, in guix terms, any configuration change to a computer, so creating your own service 99% of the time is just extending etc-service-type and creating a variable interface to fill in the config file text yourself
Creating a service as in a daemon of some kind uses shepherd and involves extending shepherd-service-type or home-shepherd-service-type with your service description, depending on whether the service runs in root or user space.
Shepherd service configurations aren’t actually part of the guix spec(https://www.gnu.org/software/shepherd/manual/shepherd.html#Defining-Services), but still use Guile, so you can interoperate them super easily.
It’s important in guix to understand lisp pretty thoroughly, and knowing how to program lisp is still a very useful skill to have so I’d recommend learning it even if you never touch guix.
I use guix because, while it has a small community, the packaging language is one of the easiest I’ve ever used.
Every distro I’ve tried I’ve always run into having to wait on packages or support from someone else. The package transformation scheme like what nixos has is great but Nixlang sucks ass. Being able to do all that in lisp is much preferred.
Plus I like shepherd much more than any of the other process 0’s
Firefly needs to hurry up and make a human-rated capsule instead of cargo farings.
I have high hopes for a company that can set up a rocket almost from scratch in 24 hours.
I still think hydrogen cells are a better long-term solution than BEVs. It’s way ahead of it’s time considering tbe infrastructure requirements, but I assume at some point after everyone is using BEVs and realizing the comparative downsides it’ll see a revival.
The ISS is aging, and for safety’s sake, NASA intends to incinerate the immense facility around 2031. To accomplish the job, the agency will pay SpaceX up to $843 million, according to a statement released on June 26.
See you guys in 2040
You could try Guix! It’s ostensibly source based but you can use precompiled binaries as well (using the substitute system)
It’s a source-first Functional package distro like Nix but uses Scheme to define everything from the packages to the way the init system (Shepherd) works.
It’s very different from other distros but between being functional, source-first, and having shepherd, I personally love it
This is because all LLMs function primarily based on the token context you feed it.
The best way to use any LLM is to completely fill up it’s history with relevant context, then ask your question.
Tango closed cause it was the one of the only studios under Zenimax that wasn’t currently making a game with “executive producer: Todd Howard” squirted all over it
There’s a weird implicit conservancy in tech circles around the dictatorial nature of corporate leadership.
It stems from this weird externalization of corporate decision making that just turns everything that happens at large companies into the machinations of the unknowable machine of capital.
“Of course they were fired, they protested in a way that disrupted the business, if the business is disrupted the machine must correct itself, and it did so by releasing the corporate anti-bodies of leadership to fire the disruptive element. Thus the machine is corrected. This is all logically sound, and thus impervious to moral inquisition.”
I’m assuming with as small as a tin foil hat as possible that the CIA and NSA purposefully do this in major closed and open source software
This feels like the same kind of issue mesa just had around the zlib update breaking downstream user programs (viewperf). If there are significant downstream issues for users you shouldn’t upgrade, even if that is the end goal.
Projects that are big and important get old and bloated because they need to try and span legacy issues alongside their attempts at newer paradigms. It’s just kind of the natural lifecycle of these projects.
There’s a great podcast series around this idea: https://www.techwontsave.us/
I’m in the Alacrity+Zellij cargo cult
I’m usually more supportive of labor protests but it’s hard to see the strike aimed at blocking this legislation as anything but selfish.
Are there details about them demanding labor concessions in exchange for this bill or is it simply “no more new doctors”?
For the usability of the clock, likely nothing.
I did mention In another comment that there are a number of advantages a round clockface provides to the creation of the clock, however.