soedirgo

> One day, game developers will package static binaries

Wouldn't you still need at least runtime linking (dlopen) to link to OpenGL/Vulkan/etc.?

While I agree with the sentiment, my impression is that the GP's point is about memory safety rather than performance. So yes, this applies for common patterns like per-frame memory in games, in which case the "it" is the arena. Otherwise, as a general rule, profile first, then optimize.

The latest edition (7th ed, 2015) actually uses 4.5 as well. AFAIK OpenGL hasn't changed too much since 3.3, certainly not to the point of being irrelevant for learning.

Can you give a source for this? Also, is it still stuck at 4.1/1.2?

Since we're in pedanticville, these aren't converses, but inverses. The converse goes "If you don't outsource X, then X is your core business".

Hey folks, this is my internship project at Supabase, which you may have heard from its HN thread that got popular recently. We lean heavily on PostgREST, which is a Haskell tool (a wildly successful one!) that turns a Postgres database into a RESTful API.

We use PostgREST through our own client library as it's much easier to use. But it's in JavaScript, and I'm part of the Rust Evangelism Strikeforce myself, and the rest is history. ;)