dvhh

one big PITA for using C with the web is string handling, the default zero terminating char array is efficient in terms of memory usage and portability, but is function handling those are full of trap, you usually end up with some custom version of Pascal string that require some special shenanigans to work with other libraries.

Debugging those would be the the primary reason why people would prefer using higher level language.

while my heart lean heavily toward A, this would serverly limit Debian contribution and would rely on contributor honesty. It might be dismissed as an attempt to gatekeep contribution. But the issue of the human cost on the receiving end of the contribution and how sophisticated attack vector it could potentially be give me some concerns about long term quality.

B being the more pragmatic, despite the (valid) code licensing concerns. but could leave some very openly LLM driven project room to contribute package.

C as a middle ground would not satisfy any party and would only push back the resolution of the status quo.

Checks out, pgrust is mainly an LLM driven rewrite with minimum supervision and guided by 100% test suite conformance.

I don't know if converting the code could be an issue with copyright, but might be contrived as plagiarism

License for test might be subject to debate, because afaik the project is merely running them.

but yes the test files should be presented under their original licence.

it does not, it basically delegate that part to lower level library for which you have to write the glue code for, there is an example for SDL.

Security by obscurity worked quite well

I might be in a niche user, but what I a mostly looking forward into an ARM laptop, would be to be silent with preferably passive heat management or as little at possible active heat management (all day battery usage is a given).

Wasn't it Frank Klepacki that composed the music for Dune 2.

Stephane Picq worked with Cryo interactive for the first Dune game.

I heard Basic is pretty good as far as embedded script interpreter

And desktop app are tuning into bloated website

admittedly mc is far from being a "modern" TUI

works with curl, maybe there is a case to either build a proxy for UDS and expose them to a browser, or open a request ticket to browser maintainers to support UDS

I would recognize sarcasm when I see it. But statistically, that could be true, considering the amount of C code running ( probably far less than COBOL or FORTRAN ), Compared to the relatively small amount of Rust code vs the amount of faults observed with it.