slept that well did you

in the best case it’s that, and you wonder why it’s not automatic. in the worst case half the packages on the system just brick themselves.

my only issue with mint is that full version upgrades are still a hassle. if that’s something that bothers you, you could switch to something else. otherwise, just keep on keeping on.

exactly.

“closer ties” is a statement of intent. “associate member” is a category of member.

…so she’s a venti?

yes. all of europe is doing that.

the eu doesn’t have anything called “associate membership” so if this passed they would have had to actually define what that means. makes sense to change the wording to something less formal but equally signifying.

the stdlib of rust is woefully lacking, proper error handling is way too verbose, the dependency chains are massive and unauditable, and all the implicitness makes it hard to reason about stuff like a.from() without proper editor support which makes code review a nightmare. i do like ccontract-driven design though. all in all i think i’ll stick to zig if i need safety.

time flies like an arrow, fruit flies like a banana.

it’s just such an odd question. you know nothing about my domain or my requirements, you just assume i can or want to use rust.

it’s all work stuff unfortunately. it’s just basic ctypes stuff though.

because i need my programs to be dynamic and scriptable?

need it to be a hierarchical thing? otherwise just cp -vur src/ dst/ >> files.txt && sort -bdufo files.txt files.txt and look in the file.

the big charm imo is that they’re eidetic. you’re not controlling a little guy, you are the little guy. you’re sat at at actual station rather than controlling someone who is. idk if looking at it through the lens of co-op party games gives the right vibe.

probably because they don’t do any themselves

no, that’s uh… basically the opposite thing.

there’s an entire genre of bridge sims out there, where you plop a few friends in your living room, link together your computos, and basically play star trek. each computer becomes a “station”, like helm, weapons, engineering, communications etc, and you collaboratively run the ship through scenarios or a sandbox, taking missions or deliwering cargo or whatever. usually there’s one person that acts as the “captain”, who hasn’t got a computer but makes the decisions, usually with a view screen (like a big tv) so you can say “on screen” when something happens. that’s not necessary though.

here i’m envisioning like a team game for four people on four computers where one person handles sensors, one power, one control, and one communication, or something to that effect. basically imagine it like sitting in the mission control room in front of your stations, with the telemetry of the probe on your screens, and you have an hour of transmission time to accomplish some tasks (like “position to normal”, “collect readings”, “reposition to retrograde”, “calibrate main array”, “transmit readings”) . it would be more about careful balancing of resources to avoid a shutdown or damage, while dealing with whatever situation may come up like memory dying, or consensus mismatches, or brownouts. you could hand-wave away transmission delays, or include like a minute of it for a bit of tension and required planning.

aren’t kde applets already built with qt?

i am eagerly awaiting the day when people learn to look things up again

i just write the critical parts in c and glue them together with python, because if it’s one thing it’s good at it’s ffi.