ManMachine
@max@manmachine.me
Image source: https://commons.wikimedia.org/wiki/File:ISO_7010_W071.svg
Author: Wikimedia Commons user Clemenspool
CC0 (http://creativecommons.org/publicdomain/zero/1.0/deed.en)
@jsatk I like languages that are *stable* and don't require me to have 7 different versions installed at once.
This textbox is a message and part of a system of messages. Java is installed on over three billion devices. Java is found everywhere, even in your car. We thought we were a powerful culture.
It's so weird that a lot of people think the quality of software is measured in how often it gets updated—it's literally the opposite.
@thomasfuchs @skynebula my usermind wet dream: finished softwares. That just work. Ideally security updates if need be. That's it.
I don't want a new UI, I don't want you to change the icon font for no other reason other than "it looks better", I don't want a new shiny feature that could be a separate app or software.
Make it libre and people will be able to make a different one, a new one, an alternate one. Fine. But don't change our tool while we are using it.
@thomasfuchs you need to reach that sweetspot where it gets touched juuuuust enough to reassure the user it's not completely abandoned. Like it gets one, maybe two patches per year
@VileLasagna @thomasfuchs It needs to be touched often enough to verify the build environment still works. We're dealing with a safety code (F77) wrapped in a VB6 GUI. We suspect the vendor has lost the ability to build the code since VB6 was EOL'd ages ago. Bugs are generally dealt with by documentation changes but there's only so long you can do that, especially if you sell the code with a QA certification that revolves around software lifecycle management.
The irony is, this code would easier to maintain and be more useful to us if it was just the dumb F77 executable. We need to run uncertainty cases involving 90+ runs - automating the VB6 GUI has involved some extremely awful and brittle scripting. We're really screwed because the vendor lost their build environment and the staff to recreate it.
@thomasfuchs I work with trains, and there, software updates cost real, actual money.
Like, figures with more digits than the number of fingers on your hand.
And that’s just for the bits that aren’t safety relevant. For updating those, you’ll need the other hand.
@thomasfuchs I would argue neither is.
Good software most of the time is actively maintained and therefore should get updated and if you have good quality control, nothing speaks against frequent updates.
It rarely happens that software is truly "finished" and shouldn't continuously be developed.
@thomasfuchs someone had a nice article about how tech today has replaced Mean Time Between Failures with Mean Time To Repair, and how that has lead to all the software that constantly breaks and gets fixed
something I've been thinking about is how, when I teach a class, I tell the TAs to never, ever touch the keyboard when they're helping a student with an assignment. not even once! because as soon as someone else is driving, it becomes real easy for the student to stop thinking and just let things happen.
kind of like what happens when we use a coding assistant.
[…] I’m anti-the branding of it as “artificial intelligence”, because it’s not intelligent. It’s a form of machine learning. “Generative AI” is just a very good Markov chain that people expect far too much from.
it has been 0️⃣ days since I had to send a corporation a nastygram about disrespecting my “reduce motion” and “do not autoplay videos” accessibility settings
the fediverse is just a bunch of neurodivergents building their own internet so they don't have to talk to the other internet
from an article about the bitcoin crash: “Bitcoin is crashing hard, reaching historic lows of well below the $70,000 mark. At the time of writing, the token is hovering just above $63,000, levels we haven’t seen since October 2024.”
Given that I personally remember people being excited that bitcoin had reached the mark of one (1) dollar, the term “historic lows” to describe returning to the state of things slightly over one year ago is rather telling about the tech industry’s lack of perspective and cultural memory…
(it’s still dropping though 😌)
@rasterweb I'm also trying to stop using "amateur" to mean sloppy and "professional" to mean high quality. That has always been a shitty dichotomy, and deskilling is only going to make it worse.
#OtD 6 Feb 1916 the Cabaret Voltaire nightclub opened in Zürich, Switzerland. Described as "history's wildest nightclub" it was the spiritual home of the often radical Dada art movement, formed by artists revolted by the capitalist carnage of WWI https://stories.workingclasshistory.com/article/10606/opening-of-the-cabaret-voltaire-nightclub
It doesn't matter whether C is good or not. It matters that if I write code in two languages that aren't C, and I want it to all be part of the same process, I need to care about C. C pervades all. You cannot escape it. C will outlive all of us. The language will die and the ABI will persist. The far future will involve students learning about C just to explain their present day. Our robot overlords will use null terminated strings. C will outlive fungi.
I just want to remind you that in 1992, the Internet cost $2.50 an hour to access ($4.00 after the first four hours a night), was three million times slower than WiFi, and nobody in your house could take phone calls while you used it. Doomscroll on THAT.
@inthehands Time Machine on two removable USB drives. One lives in your house and gets connected regularly; one lives somewhere else and you back up to that once or twice a year. All other answers are incorrect.
@fanf so, RFC 5966 said SHOULD, RFC 7766 turned it into MUST, and they still had to publish an even _more_ emphatic RFC 9210?
"The key words 'SHOULD', 'MUST', and 'GOOD GRIEF WHAT IS WRONG WITH YOU HOW CAN WE MAKE THIS ANY CLEARER' are to be interpreted …"