Ironically, AI may help get past that. In order to measure "value chunks" or some other metric where LoC is flexibly multiplied by some factor of feature accomplishment, quality, and/or architectural importance, an opinion of the section in question is needed, and an overseer AI could maybe do that.
But the method of due process may be different, and the standard of proof to meet may be different. Revoking a visa is easier for the executive branch to accomplish.
Mostly pretty standard React stuff: React + Vite + TypeScript, Tailwind for styling, and shadcn/ui (on top of Radix) for most UI components. Charts are done with Recharts.
The actual simulation and arena rendering is all custom using the Canvas 2D API, no rendering libraries there.
Maybe before 'vagrant up' you run 'sudo chattr +i Vagrantfile' to make it immutable. Seems to disallow removal of the attribute inside the VM, but allow it outside.
It could've easily been defined that the else branch runs if the while condition never had a true value at all. In fact, I think that's more intuitive.
Bluefish has had a release in October 2025 and the development page talks about gtk-3. Are you sure you've kept up to date with it? If you like it, stick with it.
You don't like those? I've always considered them a fairly elegant deconstruction of the problem domain of equality checking. DWIM languages can get very confusing when they DWIM or don't DWIM.
Where's the elegance? Equality is well defined on everything handled by those three, since they only compare the same types without doing coercion. Plus, you can't extend these to handle user types.
In fact, I recommend to newbies that their Lisp syntax highlighting shades the parentheses close to your background color. You get the best of both worlds: they fade away, but you can use Structural Editing.
