I’m a software engineering developer from Ottawa, Ontario, Canada.
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!
All praise our lord and saviour git rebase -i
!
In case anyone wants the real meanings: I am not a lawyer, read the f***ing manual, bank of america.
After years, and many languages, I still have to say Ada. Kotlin, Rust, Julia, and Nim are my current contenders to overtake, but here’s what Ada does well enough to still be my preferred tool when appropriate:
There are some situation where Ada shows its age:
func
/proc
(Nim) vs fun
(Kotlin) vs fn
(Rust) doesn’t make much difference to me, but function X returns Y
/procedure X
starts to add a lot of visual noise to a file.Here’s when I use the alternatives, and their biggest weaknesses:
Thank you for attending my TED talk :P. Any questions?
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”.