There is one (old man) in each of you, but "we" see the youth (in you) forever.
You know what this is addressing, it's not clouds, but system conversion principles. Since it is your project, but NOT your system, surprise me with a solution that I or a broader consensus would propose, on the domain of: * Discrepancies between BSD and GNU and undocumented parts in the BSD system from imported bulk of "non-OpenBSD" author-ware * A call like "get off the list" is fine too, but it's not solving the problem that pokes your eyes too. Now, let me propose a goal that is "admitting failure of upkeep in-house of important language utilities integral to the core of UNIX". Separate it in ports and strip its core to the system. Documentation is part of that, the split would be worth it on parts of the system that are exercised a lot, this one is considered moot? AWK as in the tool that compiler parsers peruse? You're _exactly_ interested in this, but it might be too late for this kind of effort.. in OpenBSD in 2025. Is it too late and too thin of an edge to walk on? awk-local(1) when? On 9/20/23, Theo de Raadt <dera...@openbsd.org> wrote: > Old man yells at cloud. Yes.
