Either continue with the current system or decide to fork time off Earth rotation entirely. The language about the "one minute" difference is rolling that can down the road cowardly and rightfully criticized by the author.
The proposed "solution" may be a possible implementation of time dissemination formats but really has nothing to do with the definition of time or the ITU.
I guess GitHub and similar providers could scan incoming commits for these in order to shield users who do not upgrade. We all know there will still be millions of those for years to come.
> The best you can do as a maintainer is to be mindful of the original problem that the solution was architected for, and extend the thing without crossing certain boundaries and assumptions.
Speaking of boundaries and assumptions, one of the most important realizations I have had about software development is the true meaning of modularity:
Software modules are the things whose boundaries limit the spread of assumptions.
I used something similar to Duff’s device to implement coroutines in C++ (pre-C++20). With some macros and using lambda function the result almost feels like part of the language.
No UB. Static analysis will keep you from doing things like using values in local variables across yields (use lambda captures instead).
Just avoid doing two CO_YIELD() in the same line because this macro uses __LINE__ for the switch case.
I wrote a tool that lets me use keys in my ssh-agent for google cloud. This way, a vm can run with minimal privileges but when I ssh in I get gcloud cmdline with full control.
It is very easy to connect to the agent and ask it to sign something.
The QuickEd external message editor for QuickBBS was perfectly usable at 1200 baud. During screen repaint it gave priority to updating the current line so it was responsive and went back to repainting the screen as soon as you stopped typing. It would ensure that it does not have too much data in the output buffer to keep latency down.
> Pledge/unveil are manifestly more successful, being used pervasively (though not really by programs which do not primarily target openbsd).
Because of their simplicity, they are easily added as a patch to a ported application. There are probably more ports using them than programs that target openbsd.
Academics can sometimes learn a lot from industry. The ScyllaDB database and its underlying SeaStar library essentially implement a userspace OS that handles the hardware very differently than a typical modern OS with phenomenal improvements in performance.
Historically, it started as a unikernel called OSv designed to run directly on hypervisors. But they eventually realized that it can run just as well on linux with kernel bypass working and io_uring and is easier to deploy.
Implementing the minimal “bootstrap” HID interface can be done without most of the abstraction layers. It’s effectively hard-wired and barely parsing of any descriptors or anything.
Nice, but there are already some de-facto standards for this. In Python I use “raise NotImplementedError”. Many IDEs and static analyzers catch TODO/FIXME in comments which works for all languages.
Low concentration HF is frequently uses in artistic glass etching. With reasonable precautions it’s not more dangerous than cleaning your drain with caustic soda. Just don’t be stupid.
Is there any way to start workers that would be guaranteed to be co-located with a specific durable object? This way they would have ultrafast access to the state it manages but not subject to the single-thread limitation.
The proposed "solution" may be a possible implementation of time dissemination formats but really has nothing to do with the definition of time or the ITU.