You should play voices of the void then. Game is chock full of random spooks with lots of very quiet and relaxing downtime, so they hit pretty hard when they happen.
You should play voices of the void then. Game is chock full of random spooks with lots of very quiet and relaxing downtime, so they hit pretty hard when they happen.
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.
Yea that’s kind of what I was thinking when I said eventually handwriting will go the same way.
If people never encounter it and do all their writing on keyboards, it’ll eventually be a useless skill as well.
From a practicality standpoint, a round clockface is easier to create a mechanical drive system for.
You can create a digital mechanical face (see: Flipboard style numerical displays) but they usually require more gears and are more susceptible to wear and tear than the gears of a round clock face.
The simplest designs for mechanical digital displays actually just take 24 hour and 60 minute/second circular displays and hide the other numerals as the clock face spins around. Technically this I suppose counts as both analog and digital?
Example:
As for electronic displays? Nah not much of a reason to use a round display unless again, you have an electric-mechanical drive and want to save on gears and parts.
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…
How so?
I genuinely don’t understand the clock-face-reading-is-a-useless-skill opinion so both seem equally important to me.
There’s nothing stopping an analog clock face from representing 24h time:
I wonder how many people feel this way about writing when everyone just types/texts everything.
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
One of the few practical things AI might be good at:
Facebook is trying to burn the forest around OpenAI and other closed models by removing the market for “models” by themselves, by releasing their own freely to the community. A lot of money is already pivoting away towards companies trying to find products that use the AI instead of the AI itself. Unless OpenAI pivots to something more substantial than just providing multimodal prompt completion they’re gonna find themselves without a lot of runway left.
NewPipe can do peertube as well
I’d say mostly energy savings and CPU usage efficiency
Ah, no not the template files for the individual containers, but the project descriptors are just compose files.
They’re 1-1 compose files.
The app just saves them as compose files and then runs docker compose in the backend.
it is EXTREMELY barebones
There’s also Yacht.
deleted by creator
The OSI just published a resultnof some of the discussions around their upcoming Open Source AI Definition. It seems like a good idea to read it and see some of the issues they’re trying to work around…
https://opensource.org/blog/explaining-the-concept-of-data-information
> Kinito Pet now playable
How the fuck is that gonna work