For AP cores where Python actually runs it’s just “arm8” and pick your incremental version on top.

If you'd limit yourself to cores implementing the Application profile of ARM (Armv8-A etc), you'd do the same and limit yourself to cores implementing the Application profile of RISC-V (RVA23 etc). In that case, you can assume vector instructions and everything else.

If you don't, you get the exact same kind of question with ARM as with RISC-V. Do you use NEON or with SVE? Or do you conservatively compile without vector instructions at all even though it could possibly result in speed-ups for some loops?

I don't think you're giving ARM credit for the ever growing pile of features which are always optional or optional only on some versions of the ISA.

For example, can you use FEAT_CSSC to improve code size and performance? Well, if the target is <v8.7, the answer is no. If it's v8.7 or v8.8, well, then it depends on whether your specific implementation has it. Only after v8.9 is it mandatory.

Targeting armv8a is the moral equivalent of targeting RV64GC insofar as it will run on any application class core. Targeting that, however, leaves a fair bit of useful ISA enhancements on the table, and so you tend not to want to do that if you can get away with it.

Micropython runs on tons of stuff and while it isnt capital-P Python, its close enough for doing a wide variety of embedded work without learning a new language/libraries/etc.

For RISC-V that would functionally be RV64GC then. And you go incrementally from there as required.

On codex the “no alt screen” option seems to help

This is way way more expensive than hetzner. Not even comparable?

Why create an array each time it iterates a Set rather than just iterating the Set?

I create a new copy of the Set because the functions called during the loop might modify it by removing elements via cleanup functions. Without a copy, iterating directly on the Set could cause unpredictable behavior.

But as the article points out, this is a naive implementation. It could be discussed and greatly improved.

Yeah like npm! Don’t think there’s ever been security issues in that.

I download all apps on my phone from the bleeding edge of npm. /s

When npm has supply chain attacks it's still news.

On Google Play Store its actually noteworthy when an app isn't some level of malware loaded with ads and questionable permissions.

Matcha has caffeine in it though?

It does, but the L-Theanine has an almost neutralising effect on the more jittery and frenetic aspects that caffeine can bring. It leaves you feeling what I would describe as more focused and calm, rather than alert and anxious

Yes, it does but not in high quantities like coffee. It gets complemented perfectly with the L-Theanine content in it.

This combo generally works well on folks that get benefits from coffee.

Raw meat? Wheat grains from the ground? Coconut shells?

no, meat from the meat aisle that comes from a cow and not with a bunch of chemicals added into it and that is in the freezer

How big is the server runtime compared to v8 under the hood?

Yes, every one of those apps is c++ powered.

When text is (clearly) non native English I think most native readers don’t even register grammar errors.

To be honest most native readers wouldn’t register grammar errors full stop.

I guess I have more awe of people who speak a foreign language at all compared to piping it through some agent malarkey.

As the other posters have shown it’s not that hard.

Most graphics specs will explicitly say how tie break rules work.

The key is to work in fixed point (16.8 or even 16.4 if you’re feeling spicy). It’s not “trivial” but in general you write it and it’s done. It’s not something you have to go back to over and over for weird bugs.

Wide lines are a more fun case…