frankly, it's really not a good idea to early-years kids assembly (double especially not fantasy assembly), if your goal is to encourage learning the field. this is why all the strong/popular pi-based educational distros and options focus on stuff like scratch, some light python (often paired with light pygame and turtle), and other low-entry-effort exploratory things like sonic-pi
many do come to explore programming topics in depth later (asm via zach games, other structural/dependency things via satisfactory/factorio, etc), and that's fine too
there is of course a longer-term balance to be struck with (and structural problems coming from) people not understanding the layers below them (cf. current nightmare of tottering piles of javascript and continually worsening app performance everywhere despite having literal supercomputers in our pockets), but "learn asm" is bad starter advice for the same reason that "you should know how to write in c" has been part of why we're in this fucking mess in the first place
depressing how Cheetoh & Co. continue to wrecking ball the shit out of everything
(wonder how long it is before the US degrades far enough that other countries start ratcheting up border/traveller defenses, compared to the current ~free rein they have (which, y'know, was owed to years of hard and soft power that the orange man is also rapidly pissing away))
and of course we all have root on the prompt, where - at will - we can just instantly impose all manner of will on the corporate vendor chatbot. y'know, the chatbot operating in a service structured as much as possible to try to do what the corporate vendor wants to desperately maintain
(it continues to astound me that anyone takes yud seriously, at all, ever)
you have so many of these! it's amazing! are you going to publish soon? it seems like it might need a whole guide of its own!
moderately barbed jesting aside, a serious question: have you spoken with any programmers/artists/researchers/.... ? so many of your comments have "part of me feels" parts hitting pop-concern-direction things and, like, I get it, but. have you spoken with any of them? what were those conversations like? what did you take away from them? what stuck with you that you want to share?
it makes me so deeply fucking depressed knowing how much near-abandon infrastructure spending is happening. minor win is that power plants can work for other things too, but it still runs headlong into a pile of other issues (transmission network, generation method side effects, etc etc)
so it's been observed by many that github's been getting worse for a while as they keep shoving copilot into every corner
with the upgrade diff review, I wanted to quickly fold closed the 485 files in the diff. I could've sworn github's diff view used[0] to have a button for this, and I know bitbucket does[1], but nope. so of course I open browser inspector to dig at elements (then quickly iterate over them with .click() in the js console)
which is when I noticed that even the elements are renamed for copilot:
which both makes me wonder my memory is right and this did used to have a button that was just overlooked in the rush for terrible chatbot shit, and makes me boggle at how astoundingly far the org is deepthroating this nonsense
[0] it's been a few years of no longer actively using github
frankly, it's really not a good idea to early-years kids assembly (double especially not fantasy assembly), if your goal is to encourage learning the field. this is why all the strong/popular pi-based educational distros and options focus on stuff like scratch, some light python (often paired with light pygame and turtle), and other low-entry-effort exploratory things like sonic-pi
many do come to explore programming topics in depth later (asm via zach games, other structural/dependency things via satisfactory/factorio, etc), and that's fine too
there is of course a longer-term balance to be struck with (and structural problems coming from) people not understanding the layers below them (cf. current nightmare of tottering piles of javascript and continually worsening app performance everywhere despite having literal supercomputers in our pockets), but "learn asm" is bad starter advice for the same reason that "you should know how to write in c" has been part of why we're in this fucking mess in the first place