@raichoo Nah, every hipster can code Rust these days. You're a good old school C programmer, be proud of it.
And programming C without falling into every tarpit on the way is not programming, it's art!
Busy week at the #dayjob but making some progress this weekend on my macOS Choosy clone for Wayland. Working on text rendering with Pango & Cairo.
HELLvetica. Like helvetica, but with like, much shittier kerning for Halloween.
So the real #C problem I'm running into right now is that I have a nested struct and a function that get the parent struct. In the function I initialize a child struct (ie. `parent->child = malloc(sizeof(struct Child));`.
Recently learned about the concept of “survivorship bias”. 🤯 I have heard complaints about this in every programming community I’ve been involved in, without knowing the actual term. It’s SO prevalent in our industry I think people think it’s just the way it’s supposed to be. I don’t supposed Evan of #elm fame is on here, but thanks to him for bringing it up and attempting to solve it!
I’m confused about when to use pointers with #C structs and when not to. As I’m searching for a good tutorial on C pointers I’m realizing that part of what makes C weird is that it’s a low-level language (memory management, no standard library) that tries to be high-level (structs, arrays as abstractions on pointers, functions as abstractions on labels, local vars going out of scope automatically, etc).
For anyone interested, here is the code in process: https://git.sr.ht/~joef/chooselicious
Being a fan of statically typed #functionalprogramming languages, it’s strange working in the langauge that introduced the problems the others aim to solve.
adding crew requirements and quarters for different kinds of vehicles.
coding with #elm is such a joy,
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!