Notices by LisPi (lispi314@udongein.xyz), page 11
-
Embed this notice
LisPi (lispi314@udongein.xyz)'s status on Saturday, 30-Mar-2024 06:15:13 JST LisPi @rq @niconiconi Insofar as you ignore glowies simply mandating the easily-pressured organization to do the compromise at the top. -
Embed this notice
LisPi (lispi314@udongein.xyz)'s status on Friday, 29-Mar-2024 07:48:25 JST LisPi @ipg @Makura On the other hand, I'd rather C disappears and Ada replaces it, for those things where space constraints are a major concern.
As for Assembly, yes, ultimately it's needed to bootstrap anything else. Even Forth. -
Embed this notice
LisPi (lispi314@udongein.xyz)'s status on Tuesday, 26-Mar-2024 07:40:51 JST LisPi @Archivist @parismarx It really shouldn't be a thing to have datacenters that aren't integrated into impact mitigation measures like that.
More generally, we should modernize UUCPnet (NNCP is a good place to start) and stop relying on 24/7 uptime for the overwhelming majority of things.
(And ideally we'd do all that with plugable transports so it can be used atop anonymizing overlay networks that do not integrate the mistakes of the clearnet.) -
Embed this notice
LisPi (lispi314@udongein.xyz)'s status on Monday, 25-Mar-2024 13:50:31 JST LisPi Considering the lack of adequate social goods in our societies, aren't basically employment contracts signed under duress? -
Embed this notice
LisPi (lispi314@udongein.xyz)'s status on Sunday, 24-Mar-2024 04:27:09 JST LisPi World: *Capability-based operating system intented for wide public use appears*
Me: Wake up $name, we're finally catching up to the 70s/80s.
World: *Project languishes unused and then dies*
Me: Nevermind, you can go back to sleep. -
Embed this notice
LisPi (lispi314@udongein.xyz)'s status on Saturday, 23-Mar-2024 08:01:00 JST LisPi @lanodan @chjara MK ULTRA was more of a human experimentation and murder thing.
And yes, "reprogramming" someone per the goals of the project is indistinguishable from murdering them and reusing the body. -
Embed this notice
LisPi (lispi314@udongein.xyz)'s status on Friday, 22-Mar-2024 06:54:51 JST LisPi @lanodan @a1ba A symbol of status -
Embed this notice
LisPi (lispi314@udongein.xyz)'s status on Wednesday, 20-Mar-2024 18:52:50 JST LisPi @Suiseiseki @icedquinn I'd be concerned with neither of those filesystems addressing data integrity. It means it has to be handled at the software level instead, which rather tightly constrains the set of programs one can use safely. -
Embed this notice
LisPi (lispi314@udongein.xyz)'s status on Wednesday, 20-Mar-2024 12:27:25 JST LisPi @coolboymew @Suiseiseki Sounds like they're doing the old silly idea of going "dd if=/dev/random of=/dev/some-drive" before finally making it into an encrypted device.
It's entirely pointless (on everything) and actively counterproductive on SSDs, naturally. -
Embed this notice
LisPi (lispi314@udongein.xyz)'s status on Wednesday, 20-Mar-2024 12:27:24 JST LisPi @icedquinn @Suiseiseki @coolboymew In truth, not pre-writing it doesn't really change anything if one didn't make the mistake of using it without encryption before.
The only difference is that wiping it with random data or even just zeros isn't an option. -
Embed this notice
LisPi (lispi314@udongein.xyz)'s status on Friday, 15-Mar-2024 16:31:37 JST LisPi @allison Yeah, I searched around for a little while before asking.
Because I'm really wondering *how* they managed to get a compliant implementation to run in 1MB.
If it's using some paging to a larger storage device or set of devices, that's one thing, but if it fully fits in 1MB with the storage being removable after? That's on a whole other level. -
Embed this notice
LisPi (lispi314@udongein.xyz)'s status on Friday, 15-Mar-2024 15:28:29 JST LisPi Is the source code for Coral Common Lisp 1.0 anywhere to be found?
I'd be curious to see it. And I'm also curious how big the system was on the floppies (the Macintosh Plus doesn't seem to primarily use a tape drive, so I assume it came on floppies). -
Embed this notice
LisPi (lispi314@udongein.xyz)'s status on Monday, 11-Mar-2024 05:20:03 JST LisPi @dalias @aburtch @JoeMcConn I thought it was a justice/vindictiveness thing. Not a literal concern with needing cannibalism. -
Embed this notice
LisPi (lispi314@udongein.xyz)'s status on Sunday, 10-Mar-2024 14:41:08 JST LisPi You know, it weirds me out how some message board programs prefer to provide some garbage API with which you need to hammer the server to create an NNTP gateway (a sensible protocol-based interface) rather than just implement it in the original program, where no hammering would be necessary and the lowest possible load would be achievable.
Surely they realize there is exactly *no* way their WebUI can ever surpass anything I can come up with in Emacs, right? -
Embed this notice
LisPi (lispi314@udongein.xyz)'s status on Sunday, 10-Mar-2024 14:12:55 JST LisPi Am I misunderstanding something or isn't youth unemployment supposed to be a good thing?
Teens and students shouldn't *need* to work. The whole notion of looking at their employment rates as a metric to lower is missing the point. -
Embed this notice
LisPi (lispi314@udongein.xyz)'s status on Sunday, 10-Mar-2024 10:51:49 JST LisPi Imagine having stable and reliable electrical and telecoms infrastructure.
I sure can't. And yet for some reason none of our hardware, software or various bits of equipment seem to be made to cope with such circumstances. I don't get it.
Why is infrastructural privilege such a common base assumption? -
Embed this notice
LisPi (lispi314@udongein.xyz)'s status on Sunday, 10-Mar-2024 06:52:00 JST LisPi Perl's lack of a built-in REPL is an incomprehensible design choice. -
Embed this notice
LisPi (lispi314@udongein.xyz)'s status on Thursday, 07-Mar-2024 11:30:32 JST LisPi @SallyStrange @neauoire Or, indeed, use trains.
Trains solve this problem. Banning cars from city premises (outside of very specific exceptions) helps. -
Embed this notice
LisPi (lispi314@udongein.xyz)'s status on Wednesday, 06-Mar-2024 19:37:51 JST LisPi @dushman @astrid It is unfortunately necessary because one has to implement all those workarounds to deal with the garbage system hosting the Emacs Lisp environment.
Normally, one would just be able to rely on the Lisp environment the system provides directly, like OpenGenera. -
Embed this notice
LisPi (lispi314@udongein.xyz)'s status on Wednesday, 06-Mar-2024 19:37:47 JST LisPi @lhp @astrid @dushman Personally I'm not so fond of a number of things about Scheme, but a few in particular are most relevant in this case.
The Scheme standards have effectively no provisions for dynamic introspection, which is a problem when one wants a long-running environment where such introspection capacity would either require adding nonstandard mechanisms (RIP portability) or foregoing them (unacceptable feature degradation).
> used more system libraries (slowly getting there)
That is a good thing exclusively for those libraries which are portable across systems, otherwise it represents a ball & chain for Emacs.
> and shipped less lisp code by default
Destroying Emacs' dynamic reprogramming and modification is a likely outcome of that (particularly given how bad the current Scheme implementations are at it, so even providing a separate REPL to the underlying Scheme isn't enough). That defeats the majority of the point of using it as far as I'm concerned.
I would sooner prefer an Emacs implemented fully in Common Lisp or Interlisp (if one must absolutely avoid CL for whatever reason).