"Unlike some of Nolan’s other films, The Odyssey is not boring, thanks to the source material, which is impossible to mess up entirely."

To imply in the first paragraph that a) Nolen's films are boring and b) that it's impossible to make a bad Odyssey movie because the source is so good, made me eye roll so hard I automatically stopped reading and closed my browser tab

> Conclusion There are 2 r's in the word "strawberry".

Not looking good so far

I guess they still use a tokenizer? Why would this kind of issue be solved? The model fundamentally can't see the word character by character like you do. For o200k tokenizers for example, what the model sees are 3 tokens: [302, 1618, 19772]. These are shown to you as ["st", "raw", "berry"] in the UI. The only way any model can infer individual characters is by using external tools or implicit knowledge picked up during training or (what many of the big labs apparently do) special training for these edge cases that fail once the next special case comes along.

"But the company can’t quite show any of that today", in case you want to save yourself a click

Wolf swears it's vegan

Why, after 6 years, I'm over increased complexity for marginal benefit. Sounds like most things developed and promoted by FANG

I would say Beej's Guide to C Programming is also excellent. Unpopular opinion, I think "The C Programming Language" feels a bit dated these days

It's also the case that _Generic is only available in C11 while this library targets C99

I'm always a fan of 80% solutions implemented in C. I think the library is pretty nice, and as someone who's experimented with trying to add quality of life features to C99 with macros I think the implementation is actually pretty clean and readable as far as these kind of implementations go.

That being said, I think the ergonomics of the approach taken by Sean Barrett in stb_ds is much nicer than the #define ALG_TYPE, #define ALG_PREFIX approach, although I'm sure it wouldn't be a big stretch to make something similar that was compatible with it.

My feeling is that you could get pretty far with something like Sean Barrett's stb_ds + Salvatore Sanfilippo's sds and then a generic algorithm library like this one

I think the difference is that stb_ds is a datastructures library and this is for algorithms. This algorithm library will also look like a completely regular C library if you just use separate .h and .c files to instantiate declarations and the implementation, I think it's very clean.

I meant more from the perspective that stb_ds achieves type safe generics in C using macros but without using defines.

It would be interesting to see if something similar could be achieved for an algorithm library.

It would be interesting but I prefer the approach in this post - because the templating macros are isolated out into a "module" and it does not great spread across the user code.

Summary could have been:

"Man makes a stand against more Blizzard bullshit, mistakenly assuming that someone in management has a soul, gets fired"