[H4ZB7]

it doesnt solve the problem

give me functions that output typed data. none of this string parsing shit. the sole fact that they have syntax to call bash: $() makes me not want to use this ever. this is why every single effort like this is wasted. i used to get excited by these projects and after about 2 of them i realized it's always a bunch of crap duct taped together, and also bends over to be compatible with un*x and so everything is ruined.

they're also often so poorly implemented, like with those early fancy python shells they'd go beserk if one command you execute goes into a time consuming process (or infinite loop) whereas why the hell can i not just run another command below while waiting for the one above to complete? this is the thought i had in 2008. i could have made something better out of my ass. really, there's no other way to put it.

here's another thing: a language console should operate on semantic objects, not text. as in, you move objects around to program in it. editing code by typing one character at a time is too slow. no amount of vim or emacs fixes this. in fact, we can just scrap those un*x garbage (along with the rest of un*x) while we're at it, when implementing an OS that works on actual meaningful data instead of text, and semantic objects instead of a language represented by text.

[ratboy666]

But, bash has this... (job control)

: root@llana fred #; dd if=/dev/sda of=/dev/null

^Z

[1]+ Stopped dd

if=/dev/sda of=/dev/null

: root@llana fred #; bg

[1]+ dd if=/dev/sda of=/dev/null &

: root@llana fred #; jobs

[1]+ Running dd

if=/dev/sda of=/dev/null &