C-programmer

It's interesting to compare this series to the actual source code of sqlite. For example, sqlite uses a LALR parser generator: https://github.com/sqlite/sqlite/blob/master/src/parse.y#L19...

And queries itself to get the schema: https://github.com/sqlite/sqlite/blob/802b042f6ef89285bc0e72...

Lots of questions, but the main one is whether we have made any progress with these new toolchains and programming languages w/ respect to performance or robustness. And that may be unfair to ask of what is a genuinely useful tutorial.

Inspect element on https://web.archive.org/web/20240827031455/https://ottertune...

For more context:

> I'm to sad to announce that @OtterTuneAI is officially dead. Our service is shutdown and we let everyone go today (1mo notice). I can't got into details of what happened but we got screwed over by a PE Postgres company on an acquisition offer. https://x.com/andy_pavlo/status/1801687420330770841

`write` can format your disk if a trickster sets LD_PRELOAD to a malicious shared object.

The quintessential project for programming newbies. I implemented it when studying Haskell.

https://github.com/vladov3000/boids-hs

Yes, and I've seen them in production. Once you learn the rules, you can parse them reasonably well in your head but it is still really confusing at a glance.

> I genuinely believe Groq is a fraud. There is no way their private inference cloud has positive gross margins.

> Llama 3.1 405B can currently replace junior engineers

I'd like more exposition on these claims.

Genuinely, why?

- For new code, all of the functions [here](https://libc.llvm.org/gpu/support.html#libc-gpu-support) you can do without just fine.

- For old code:

  * Your project is large enough that you are likely use using an unsupported libc function somewhere.

  * Your project is small enough that you would benefit from just implementing a new kernel yourself.

I am biased because I avoid the C standard library even on the CPU, but this seems like a technology that raises the floor not the ceiling of what is possible.

ffmpeg has libraries. Why are you forking a separate process to call a single function? This is a very common problem I see in high level languages with poor C interoperability. Although cgo works fine, so what gives? Less code for more problems.