pleroma.debian.social

Jonathan Dowland | @jmtd@pleroma.debian.social

Principal Software Engineer on #OpenJDK #RedHat. #Debian developer (dormant). Computer Science PhD student. Amateur Computing historian (Computer Science and H/W, esp. Commodore Amiga). Guerilla archivist.

@jernej__s fair enough, sorry! It is a good illustration of that. I just got distracted by doom trivia

@whynothugo that’s good to know, thank you!

@jernej__s indeed. FWIW, to play doom “faithfully” there are much better options nowadays. Windoom broke a bunch of things (apparently it was ported by Gabe Newell in his time at Microsoft)

@lina @trix and a windows counter example: doom (1993) same age as Mikko’s example, won’t run in modern windows today, most DOS stuff won’t I think, and all the 16 bit stuff won’t

@lina @trix oh I agree: they’re definitely a different magnitude of complexity. The question I guess is, would the average ancient binary someone might want to run today work or not? Need more data

@lina @trix the last time I tried to run old binaries was a while ago, and it was various Loki games binaries from the early 00s. Short version: they don’t work today. Some of the issues can be worked around with effort. YMMV

@trix @lina note that mikko didn’t have to find a 30 year old libc to run alongside the binary

@nettles I think my first lines probably all land in the 50-60 character region. Including tag and branch names in log output occupies the first 60-80 columns just by themselves for most repos I deal with.

@nettles I’m often irked by the 50 column highlighting for my commit messages. I haven’t looked up what tool it’s to benefit: I guess shortlog output on an 80-char wide terminal? Or email subjects?

@bencurthoys @sbi @cstross @danjac @timbray that’s a lovely little honey farm. But I’m not sure it’s apocalypse-proof

@whynothugo @jwz but elsewhere, Wayland was a golden opportunity to make something truly great. But sadly I don’t think its bugs will all just get fixed; it has fundamental, intractable design flaws (I’ll dig out the references if I really must). So for incumbent X users, the argument is to moved from one intractably broken (but somehow used for decades) system to a new, also broken one. 2/2

@whynothugo @jwz I accept that X is broken, and it’s a miracle it’s survived this long. And FOSS didn’t design it, we inherited it in the first place. I’m fairly sure some folks will step up to keep it on life support, at least for some platforms (and they’ll be ridiculed for it, like the sysvinit lovers). FWIW it makes perfect sense to me to focus on wayland for greenfield like your platform. 1/2

@jwz @marcan @whynothugo this question is posed totally inside out anyway. The argument is *why switch*? What’s the value proposition? The strong-arming and X11-shaming is because the value proposition of wayland is weak. I’ve switched to it twice, and back, as the list of broken things each time was absurd.

Playing around with both Kakoune (https://kakoune.org/) and Helix (https://helix-editor.com/): pleasantly surprised that they both include Zenburn themes OOTB (https://kippura.org/zenburnpage/)

@mhoye that’s cool. I used to have a shell alias to gnu grep to do the same thing. Something weird like this works (telling I can’t remember exactly what): grep —color “($@|)”

Ok Google: please publish your DKIM secret keys – A Few Thoughts on Cryptographic Engineering

https://blog.cryptographyengineering.com/2020/11/16/ok-google-please-publish-your-dkim-secret-keys/

@jwildeboer :) I’m glad it went well. I did my first customer thing in forever last July, (in the fair city of Ingolstadt) and it was hard, daunting work!

@jwildeboer that’s a lot of champagne for one person ;)

»