incidentally: when you're using the shell in *nix, you're programming. there's a reason it's called shell scripting. and i think some of the complaints non-technical users have with learning to code can also give some insight into why the shell is often so user-unfriendly for that demographic
if you truly want a "year of linux on the desktop" someday, that's worth thinking about
@typhlosion Plan 9's #acme and #rc make shell scripting a whooole lot easier
heck, #Plan9 itself is infinitely more pleasant to use than Linux
it could definitely be modernized but it's a much better starting point than anything else I can think of (except maaaybe something based around a single language from the bottom up where the OS is just the runtime and programs can share references to structures more easily, but it'd have to have a very good type system)
@grainloom @typhlosion IIRC, #TempleOS had something similar to this where the OS, apps, and shell code were all in #HolyC
@USBloveDog @typhlosion it'd have to be something that prevents unauthorized memory access :/
@typhlosion fun thought: visual "control flow" diagrams (probably the lowest possible form of "visual" anything) are exceedingly rare to see outside of disassembling; useful when taking things apart yet strangely absent when putting them together
It is beneficial to corporations to keep the control that they have, and encroach further on what they don't.
User friendliness via interface is a viable commodity, but not access to higher control functions that would deter corporate interests.
Corps HATE modding, because it can use parts and procedures that the corps do not control.
@typhlosion disagree
@typhlosion That's okay, I don't either
@typhlosion this is unfortunate cuz my stance is Kas is a smart cookie and i trust her completely
@rebexorcist oh no this is a mistake
i guess i'm making it sound like i have all the answers or something but really i'm just thinking out loud, sorry about that