That would be an excellent idea. But I feel like an even broader community should be created. Like a generic book club, but for code bases! Could even have a small handful of different code bases on the go at a time. I'd love to get to know lemmy's, but also e.g. neovim, or even unciv :)
Maybe one day it could even start tackling Moby Dick!
Beej's guides are absolute classics. The networking guide is also amazing. Definitely worth the read.
Except for one issue: it's an even width, so now we have the inevitable attempt to make it off-centered but pointy leading to a leafageddon. Oh well, can't have everything.
What are factions, and where do you search them? I don't see anything in the UI?
EDIT: found them under a link under info. Thanks for setting the faction up!
Yeah, when I was picking a scale I intentionally looked for one with minimal AA cause I was worried about that. The 180-wide version was full of it, as was the 99.
FYI: I'm starting with the outline of the left half of the leaf. I have to go to work soon, but hopefully there'll be enough outline for the rest to be filled in (just mirror it one pixel over).
Wait until you learn about the shell specific /dev "files" like /dev/udp and /dev/tcp (which can send/recv IP traffic as if from a file)!
Sadly front end, like "High Level" is a very relative term. For example, in compiler design, the bit that parses code is called the "front end" since the "back end" is what emits machine code. I think that's what they mean here, the "front end" that understands D3D8 code has been added, presumably there is also a "back end" that converts the parsed/analyzed D3D8 code into valid opcodes for consumption by GPU/CPUs.
In the other direction, a UI/UX is sometimes called a "back end" when it is part of a more complex embedded project where physical controls are the "front end".