Notices by Josh Triplett (josh@social.joshtriplett.org)
-
Embed this notice
Josh Triplett (josh@social.joshtriplett.org)'s status on Saturday, 13-Apr-2024 23:53:55 JST Josh Triplett
(Using Mes to bootstrap the world is still a good idea, though. But the tools used for bootstrap don't need to be the same as the tools used for day-to-day builds.) -
Embed this notice
Josh Triplett (josh@social.joshtriplett.org)'s status on Saturday, 13-Apr-2024 23:53:55 JST Josh Triplett
I don't think it's sustainable to force an older version of anything, except for bootstrapping (e.g. use old Python to build new Python).
Scheme would be less work for bootstrapping but more work for users (since most users won't be using Scheme for anything else). I'd rather have less work for users, which means more potential reviewers.
It's challenging to make Python code opaque, and doing so is automatically suspicious.
(As an aside, when I'm saying "Python" I'm not automatically assuming "to run Meson". Meson has some nice properties, but is not the end-all be-all of build systems, and seems far too opinionated to be a universal build system for everyone.) -
Embed this notice
Josh Triplett (josh@social.joshtriplett.org)'s status on Thursday, 02-Nov-2023 14:20:46 JST Josh Triplett
That seems like something that could have been standardized through data rather than code, though. For instance, a standard interface for power supply hardware, with enumerable power lines, and tables that say "this device is attached to this power line".
Having *tables* in firmware seems like a great thing, for everyone except vendors who think it'll destroy their ability to "differentiate" and "value add". Why give vendors a language to drive arbitrary non-standard functionality?