@astrid@jiub Just one lacking most of the actual things that distinguish Lisp from others.
It is impossible to fix bloat and syntaxic problems in Javascript because one doesn't have the ability to work on the AST from within the language itself. One needs to beg the standard bodies for it.
JS' design is closer to Self from what I've heard, too.
@icedquinn@dangerdyke@p@yassie_j > i'm not sure wdym unix is designed in a way that can't be hardened. openbsd does it all the time. grsec did quite well, its just they were tired of working on it for free and the linux foundation had zero interest in merging it when it was donated.
The UNIX model of memory-unsafe C APIs is asking for trouble and memory-unsafe monolithic kernels have major ambient authority concerns.
OpenBSD claims to have few remotely exploitable bugs in the default install, but that same systems *requires* additional software to be useful for most purposes people want it for, so the default install's claims & state don't exactly mean much beyond that it meets at least the lowest bar one should apply to OSes.
Converting a system to using capability addressing pervasively instead of the C APIs would break compatibility with POSIX & UNIX, so it is consequently impossible to properly harden UNIX.
I'd been considering how to do deal with the BIOS/EFI layers.
All the rest can be handled with btrfs (GRUB still struggles with subvolumes, but using a btrfs filesystem without those exclusively for /boot seems fine to me).
Mostly because to maintain integrity/correctness, it makes the assumption that the drives' firmware can be relied upon to detect and signal fault/error conditions. The problem is that this has never been the case. The blackboxed firmware is not reliable.
Hardware RAID, once upon a time, had checksum data appended to data sectors to detect integrity errors (the 520 bytes vs 512 bytes thing) independently, but software RAID afaik never duplicated this.
Or basically, if you don't have the money to replicate an ideal enterprise-like environment, ZFS rapidly shows where it falls flat and btrfs doesn't. bcachefs likewise doesn't and attempts to fix some of the limitations which btrfs has (such as the lack of caching support, etc).
It used to have actively supported explicit transactions. Making the use of a filesystem for datastorage *not* an absolutely idiotic & unreliable notion, for once.
And then they went and deprecated it because devs are idiots and don't understand why transactionality is absolutely essential.
@Senator_Armstrong Those miscreants that seek the supremacy of copyright over art and culture, even if they have to kill it in order to achieve that goal.
@Senator_Armstrong Shared copies aren't lost sales though, there are various reasons for this, particularly when international borders start to get involved (licensing, laws, censors, all sorts of nonsense).
I'm not disputing that the labor of creating art should be valued and those doing it paid.
I do however fundamentally disagree with any model founded on an oxymoron like "intellectual property" which ignores the actual value involved, where it lies and the interactions possible with artistic materials.
(It also ignores the many negative impacts which the imposition of the supremacy of its fiction involves.)
Hi, I'm Lispi, Lisp (Technomancer) Wizard (to eventually be).You might know me from @lispi314@mastodon.top I like Free Software, #Emacs and resilient computing a lot.I also like anime girls, animes with cute girls doing cute things and artwork with them too. Cute stories are good too.Some Pins:Software and Assumed Privilege, common problems: https://mastodon.top/@lispi314/111253066257920146Writing Privacy-preserving software & services 101: https://mastodon.top/@lispi314/110849018589421824#Kopimism #FreeSoftware #CommonLisp