One of the (small but annoying) issues that bugs me in these years is how to use my little, sparsed, free hours as a pretty experienced programmer to improve the world my children live in.

For sure, primum non nocere: I don't want to contribute to #commons that are going to be used against them.

So my work must be totaly useless or even toxic to #BigTech and #LLM programmers, for example.

But even within such constraint, I struggle to decide if I should work on something people can use today to protect themselves (e.g. a simple web UI for doh.cgi ) or on something that might turn to be useful in a (probably remote) future, either directly or by widening the #Overton window, such as #JehanneOS or a new programming language designed to be LLM resistant (and again, likely toxic).

The engineer in me push me torwards something that is useful here and now. The hacktivist in me push me towards more "pointless" (hopeless but hopegenetic?) hacks.

And so I work a little on a project, a little on another, slowing down each one.

Is this an issue to anybody else?
If so, how do you address it?
doh.cgi: Top-level Files of tip

One of the (small but annoying) issues that bugs me in these years is how to use my little, sparsed, free hoursas a pretty experienced programmer to improve the world my children live in.

For sure, primum non nocere: I don't want to contribute to #commons that are going to be used against them.

So my work must be totaly useless or even toxic to #BigTech and #LLM programmers, for example.

But even within such constraint, I struggle to decide if I should work on something people can use today to protect themselves (e.g. a simple web UI for doh.cgi or something that might turn to be useful in a (probably remote) future either directly or by widening the #Overton window, such as #JehanneOS or a new programming language designed to be LLM resistant (and again, likely toxic).

The engineer in me push me torwards something that is useful here and now. The hacktivist in me push me towards more "pointless" (hopeless but hopegenetic?) hacks.

And so I work a little on a project, a little on another, slowing down each one.

Is this an issue to anybody else? If so, how do you address it?
Prima commit in #JehanneOS dopo 5 anni, per permetterle di compilare correttamente con #Debian Trixie.

brutto segno.

Sviluppare sistemi operativi è un hobby pericoloso.
@[email protected]

These days I feel a urge to resurrect #JehanneOS. Even better, restart it from #9front #MIT licensed sources adding my own code under the HackingLicense, maybe with a little addendum to explicitly leverage the Article 4(3) #CDSM’s opt-out mechanism.

@[email protected]
@[email protected]

I used to believe so.
So much that years ago I created #JehanneOS ( http://jehanne.h--k.it/ ) to cleanup the (few) #Plan9 issues I saw and make it both simpler and more poweful.

However after years working on it I gave up, mostly because I realized that the language of Plan 9 is just as arcane and elitarian as UNIX one.

Awk? Grep? Xargs?

Why do we use such arcane words?

Plan 9 is way simpler than modern unices such as #Linux or #BSD, but still too arcane for most people to learn.

#OberonOS was simpler, for example (but lacking important concepts such as hierarchical filesystem and proper multiprocessing).

We should start from scratch I'm afraid, learning from past errors and trying new appraches.

@[email protected]
Jehanne is moving!

Jehanne - Jehanne is moving!

Jehanne Operating System

That moment when you realize that your operating system has always implemented System V ABI the wrong way, BUT applied the error coherently everywhere, so that everything worked fine anyway.

#JehanneOS #Jehanne