Medium seem to have made the decision to garden-wall most of their stuff behind a login, and break the sign up process (for my mobile browser, at least)

@pwaring take a look at “honk” (minimalist, Go)

@foosel we use one of those for managing trips to the beach: seems to handle really well on sand too

@szbalint @algernon I mean it is abandonware, but is this helpful? There’s still million of X users and will be for some time to come.

@mairin aye that’s true, one couldn’t rule that out from happening.

@mairin if you chose to stay, it seems that replies can be written in any language. you could start a thread with “Irish thread incoming!” And write the Irish in self-replies to that post. However I’d understand if you didn’t want the faff of doing that

New blog post: FreshRSS https://jmtd.net/log/freshrss/ #containers #software #web

@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.

@whynothugo sorry for the delay, it took me a while to re-find this. https://dudemanguy.github.io/blog/posts/2022-06-10-wayland-xorg/wayland-xorg.html

@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