Sametti
@sametti@transspecies.online
My problem. Is that I have the capacity to write my own open source replacement for any one single software program that goes bad. But if all the software goes bad at the same time. I do not have the capacity to rewrite all of them.
I look at projects like uxn/100rabbits, who applied retrocomputing ideas to actually write an entire self-contained software environment where they wrote minimal versions of all the tools they need. And I respect that a *lot*. But they spent years on that. And I'm starting now. I didn't realize I'd have to do this. I foolishly assumed I could spend my spare years on frivolities like "creating art" instead of preparing for the software apocalypse. Shoulda prepared for the software apocalypse. idk
RE: https://mastodon.social/@emaytch/117243019587276446
It's shockingly easy to forget how quickly Linux went from "zero" to "basically passable end user OS". This didn't happen between 1991 and 2025. It happened between 1991 and like, 1997. And it was with a much smaller community than is potentially available on the Internet today.
We can replace Linux. It's only an organizing problem.
@mcc it feels weird bc it essentially feels like we’re reapproaching a point where computer ppl need to relearn organizing skills that ppl had to do to make these things happen in the 70s, 80s, 90s, that we thought were all just solved problems already.
or adjusting to different realities, whether that’s resigning ourselves to the status quo, or working with projects thay don’t do exactly what we want or need, so we have to adjust ourselves to the tools in the meantime
@mcc A thought on replacing Linux... one could start putting together a desired common userspace stack (core libraries, languages, runtimes, tools, etc) sitting on top of a bare bones linux distro (whichever works best / is least objectionable) in parallel with building or adapting a new kernel to support the same userspace stack. I feel like one area that is worth exploring to make a potential next-open-platform more robust long term is simplifying and unifying a core userspace stack for it.
@swetland A thing important to me is like… when I use Linux I put up with a whole bunch of bullshit because I get an interoperating ecosystem out of it.
I *hate* sh scripting. I need a system with sh scripting because that gets me the ecosystem.
Now the ecosystem is a problem. If you want to rewrite/fork everything (either to get rid of "AI" or to get rid of C) the Unix philosophy is your enemy. Easier to fork a few big tools than hundreds of small ones.
…Does that mean I can/should kill sh?
@vivithecanine @swetland I love perl. I'd love just using perl for scripting instead of bash/cut/sed/etc. I do not think in good conscience I can create a situation where other people are forced to use perl because of my decisions.
I think python is very good and is better for shell scripts than people expect if you use subprocess2 and have a good wrapper function for it. But if the goal is avoiding programs with "AI" contributions, I don't know what I can expect out of Python on that near term
𓀨 he is making a computer chip
𓂐 bad airplane pilot
𓃰 elephant!!!
𓇰 robot gripper!
𓇴 snake attempting to steal a cymbal
𓈝 television!
𓈲 how are they balancing all that?
𓉪 the snakes have eaten the transistor.
𓋲 swingset!!
𓎃 bowling pin
𓎚 WRENCH!!!
𓏞 traffic light!
observation. in programming / computing, there’s a hundred people who want to tell you that You’re Doing It Wrong even before you started, especially if you’re young (or glob forbid, queer!)
in videography (which I’m enjoying right now) you can show others an absolutely unhinged setup that looks like it may fall apart at any moment, and they’ll still be like “oh gosh, this is cool!”
i think that we, as IT people, have a lot to learn in not speaking up unless you have something nice to say
N33R "violently concerning" ⚸ 🩸
[any/all but I will silenty judge you if you use the wrong ones] » 🌐
@N33R@fops.cloud
N33R "violently concerning" ⚸ 🩸
[any/all but I will silenty judge you if you use the wrong ones] » 🌐
@N33R@fops.cloud
N33R "violently concerning" ⚸ 🩸
[any/all but I will silenty judge you if you use the wrong ones] » 🌐
@N33R@fops.cloud
in the interests of openness and transparency, I have prepared this report about my time in Germany for #EF30 last week. please let me know if there’s any more info you want to see 🫡
@sametti i actually didn’t end up buying anything in the DD :( I only got to go in on the last day, and the stuff I was interested in was all sold out
but there is one large purchase from when I went to the local gay paraphernalia shop and got a new chain collar, a T-shirt and a tank top
~ party release ~
I recreated the Commodore 64 Programmer's Reference Guide, Chapter 5 in troff(1).
Learn yourself 6502/C64 assembly!
Print-ready PDFs included.
Please share!
/ht @evoke
#commodore #c64 #assembly #programming #typesetting #bookbinding #evoke2026
I love hanging out and drawing with friends because it produces absolutely unhinged things like this:
Cyclical bisexual who is constantly monitoring her own Kinsey number, and dyes her hair blue when she's feeling it for women and brown on months she's interested in men
This system helps prevent misunderstandings at the club
LOL remember caring and talking about Kinsey numbers? Remember when you still believed in gender
N33R "violently concerning" ⚸ 🩸
[any/all but I will silenty judge you if you use the wrong ones] » 🌐
@N33R@fops.cloud
History