4 ms·
I'm aware it used to be that way, but it's long been fixed It's fine to hate Unix, but you should update your examples :)
by chubot 2y ago
I'm aware it used to be that way, but it's long been fixed
It's fine to hate Unix, but you should update your examples :)
- DonHopkins 2y agoI'll update my examples when your examples of how it's been fixed don't use the same arcane syntax and semantics as the 48 year old Bourne shell. That's the whole point, which you're still missing. > $ bash -c '[ $((1 + 1)) = 2 ]; echo $?' Not even Perl uses that much arcane punctuation to test if 1 + 1 = 2. As if [] isn't enough, you've got to throw in two more levels of (()), plus enough grawlix profanity for a Popeye comic strip. And people complain Lisp has too many parens. Sheez. https://en.wikipedia.org/wiki/Grawlix https://en.wikipedia.org/wiki/Grawlix There's even an emoji for Unix shell syntax: https://www.compart.com/en/unicode/U+1F92C https://www.compart.com/en/unicode/U+1F92C
- Datagenerator 2y agoWhat are good shells in your opinion?
- anthk 2y agorc and 9front's philosophy. Unix, but better and removing all the cruft.
- DonHopkins 2y agoI prefer ITS DDT (aka HACTRN), with its built-in PDP-10 assembler and disassembler, that lets you do things like your login file customizing your prompt in assembly code to print the time by making system calls, without actually spawning any sub-jobs to merely print the time: https://gunkies.org/wiki/ITS_DDT_Guide https://gunkies.org/wiki/ITS_DDT_Guide ..PROMPT holds the instruction which DDT uses to type out a "*". You can replace it with any other instruction. To use "%" instead of "*", deposit $1#%$> in that location ($> to avoid clobbering the opcode without having to know what it is) If you have to use arcane syntax and grawlix profanity, you should at least have direct efficient access to the full power of the CPU and operating system. https://en.wikipedia.org/wiki/Incompatible_Timesharing_System https://en.wikipedia.org/wiki/Incompatible_Timesharing_Syste... https://en.wikipedia.org/wiki/Dynamic_debugging_technique https://en.wikipedia.org/wiki/Dynamic_debugging_technique https://web.archive.org/web/20061011004003/http://www.sigfs.org/its-reference/its-reference-1.5.html#tth_chAp7 https://web.archive.org/web/20061011004003/http://www.sigfs.... https://its.victor.se/wiki/luser https://its.victor.se/wiki/luser https://www.hactrn.net/sra/alice/alices.pdp10 https://www.hactrn.net/sra/alice/alices.pdp10 https://gunkies.org/wiki/Incompatible_Timesharing_System https://gunkies.org/wiki/Incompatible_Timesharing_System (I recognize that photo I took of MIT-MC at the MIT-AI Lab!) https://gunkies.org/wiki/File:Mit-mc.jpg https://gunkies.org/wiki/File:Mit-mc.jpg Even the Apple ][ Integer Basic monitor ROMs had a build-in mini assembler and disassembler. https://www.ldx.ca/notes/apple2-notes.html https://www.ldx.ca/notes/apple2-notes.html
- cruffle_duffle 2y agoI keep submitting PR’s to get my assembler extensions in Fish and ZSH but so far no avail. Ideally all scripting should be done in single-clock-cycle assembly statements. I mean it makes write-only languages like Perl look like beautiful prose but it’s hard to argue about efficiently setting the 20 environment variables used by my terraform jobs with a mere 20 clock cycles. It may seem silly but every clock cycle truly matters.
- thedrexster 2y agoit's not silly! <3
- pjmlp 2y agoIt has been fixed on Linux distributions, which aren't UNIX. And even that, only bash, because I wouldn't consider the state of X Windows and Wayland fixed in any way, shape, or form.
- jillyboel 2y agoUNIX is dead, no one cares anymore. It's just Linux now. Your examples and complaints are both outdated and not in good faith. For all the weirdos smashing that downvote button: How about you name me some UNIX distros you have ran in the past year? Other than Linux, OpenBSD (~0.1% market share btw) and ostensibly MacOS (which we all know has dropped any pretense of caring to be UNIX-like many years ago), that is.