mgaunard

You're missing the fact that "multiplying a digit with a number" is not a single operation.

I feel like people use this "remember the Vasa" idea every 6 months.

Yes, we all remember the Vasa, and understand how it applies to any untested overengineered idea.

how is it obfuscated? It's literally written as plain black monospace text on a white background.

Pretty sure any AI can solve it in 20 seconds.

99% of all loose ties are due to people doing a granny knot instead of a square knot.

There is no shared lineage here. Some of the people who worked on sender/receivers indeed also worked at Nvidia on Thrust, which never had anything to do with coroutines.

most of those are just bindings, trivial work.

An actor does not have a queue; that's again the whole point I already made: it's event-driven, things are decoupled and the actor is not aware of how control flow happens.

Regardless, when the queue which exists and is per-thread is empty, the program terminates.

Why is the AI only able to reach 17%?

Surely it can just keep iterating until it implements the full test suite?

Well in mine for example, threads are pinned to a core and always spin, and actors are pinned to a given thread (you can have an arbitrary number of actors per thread, they're just objects), so "waiting" is certainly not something you'd use to describe the setup in any capacity.

That sounds like a misunderstanding of how the actor model works. An actor doesn't wait. It's an event-driven system, it doesn't get to own and decide when messages get fed to it.

not really, they yield to other event sources, which is the opposite of waiting (which blocks forward progress and is a violation of real-time guarantees)

yield to the event loop

Coroutines aren't great, even C++26 is explicitly avoiding them for its foundational concurrency model.

In any case a good concurrency library doesn't need more than C++14.

essentially this is a mini-ISPC?

boost unordered flat map didn't exist in 2016 (nor 2019).

How does it compare to boost unordered flat map?

Looks like the benchmarks were last updated in 2019.

You're suggesting pre-filling future data based on extrapolating current rules (up to an arbitratily unknown high date) instead of using a constant.

I don't really see how that is a good approach in any capacity.

Never heard of DST? The authoritative time is constant in the local time zone, but needs to change in UTC twice a year.

This is the exact reason people store time in local time zones.

Also remember the date/time where DST switching occurs is entirely timezone-specific, and it's not necessarily the same pattern every year (as demonstrated with British Columbia).

A whole lot of nonsense from a web guy.

Please, keep using JWTs, they do their job well: giving you an access or ID token that you can pass between applications and trust based on cryptographic signatures from an identity provider.

Film is 24fps which is lower than PAL.

The 30fps of NTSC is actually associated with "cheap-looking" video.

10% (and even 5%) is still significant.

PAL and SECAM are also interlaced.

Except PAL/SECAM don't have any of the color issues of NTSC.

macos is not common?

Isn't this essentially normal AI usage and what everyone has been doing for 6 months?

Why so much love for NTSC and so little for PAL and SECAM?

Aren't there several bitonic sort network implementations that are vectorized, Intel's in particular?

Why not compare against that?

Interesting, but pretty limited corner case. Would compilers even identify those 28 values and do the transformation?

That's only valid to do if the reciprocal is representable exactly.

I had somewhat similar questions asked of me in the 2000s, and I still ask similar questions today.

Waltz is 19 quid, but it's arguably the best cocktail in London.

The Connaught is up to 40, but more of a fancy establishment.