> If I set my alarm for 7:45 am, I need it to ring when the clock says 7:45 am, wherever in the world I happen to be.
Oh I desire more from my alarms.
Ideally I would be able to set an alarm for 7:45am and mark it "all timezones by then-local clock" ... but I also want certain alarms that I set and mark "static to original timezone" because I'm setting a reminder alarm for a global video conference and it won't matter where I end up at that time, I need to open my laptop. ... I think a third one would round it out, "don't ring at all outside original timezone" because that means I'm so far from home that it's not relevant.
I play around with quicklisp to develop and tinker.
To test and deploy, I generally use Guix [0] to express a package for my application which pins dependencies to exact versions and optionally can run in a container. I have Guix installed on top of Ubuntu.
This is hobbyist and experimental work so it's not battle-tested.
Yes. A sequence of consecutive hashes would match to a TV show or movie identifier in a local database; and that identifier is all that needs to be uploaded until there's a new TV show or movie identified.
I've lived in the US and UK and noticed what I think is a tiny cultural difference -- that signs giving instructions in the US tend to be brief and contain the instruction only; whereas in the UK I thought I saw more that add some text for a brief explanation or reason, if it wasn't obvious.
I agree that real is better, but "fake" scenery lets you explore and ride virtually in all kinds of natural and urban surroundings, which might be interesting to some people.
> you trust the websites of your Linux distro vendor, but not netboot.xyz
Well... yeah... that's not that crazy of a position to take.
Not saying there's anything wrong with netboot.xyz, but it's a question of how many cooks to let in the kitchen, and how many public eyes are on each cook.
Even for porting there's a bit of ambiguity...
Do you port line-for-line or do you adopt idioms of the target language? Do you port bug-for-bug as well as feature-for-feature? Do you leave yet-unused abstractions and opportunities for expansion that the original had coded in, if they're not yet used, and the target language code is much simpler without?
I've found when porting that the answers to these are sometimes not universal for a codebase, but rather you are best served considering case-by-case inside the code.
Although I suppose an AI agent could be created that holds a conversation with you and presents the options and acts accordingly.
I wish I knew how to communicate that change to folks. There is a lot of history on many of the forms that exist in common lisp. And much of it is far more practical in origin than I expected going into it.
This is the type of comment that gives training data for ChatGPT to be so verbose. Ha!
reply