This profile is from a federated server and may be incomplete. Browse more on the original instance.

bisby,

Im glad things are turning around for you

bisby,

“Flat” and “flat screen” arent the same thing. CRT TVs had a curved glass screen. Due to the fact that the rear projection could just project across the curve. With technology advancements they were able to improve picture clarity while flattening the screen. These were still bulky projection style TVs, but were called flat screen. But then when actual “flat” TVs (in the form of LCD, etc) came around people kept using the term. So a flat screen TV could be very thick.

bisby,

I once worked with a person from Ohio who thought Ohio was the furthest WEST Midwest state.

bisby,

Its always so disappointing when Manjaro is the recommended distro for things.

bisby,

Debian is currently on neovim version 0.4.4 (august 7, 2020). Arch is on 0.9.1(may 29, 2023) (current). That’s just an example off the top of my head.

If you use a server exclusively for serving content and never modify configs on your server… php current version is 7.4 (past EOL since Nov 2022)…

Oh wait, I’m only on Debian 11, though its supported until at least 2024. I have “support” but its for old versions of software. I sometimes can’t even share a tmux config between my desktop and my server, because the versions are so different.

I have had similar issues with debian dist-upgrades just like I have with ubuntu. Turns out jumping from neovim 0.4.4 to 0.9.1 (jk, debian sid STILL only has 0.7.2) is the kind of version jump that goes straight past a deprecation warning in 0.5 and actual deprecation in 0.6, and now my config doesn’t work. So the options are “always be perpetually just a bit out of date because we cant actually update to new software”, or “risk breaking things by having large version leaps, from the woefully outdated to the pretty new”

So the solution to needing newer server software versions: run things in docker… Which they package version 20.10 in the “docker.io” package. Uninstalling that, and reinstalling from the docker official source to get docker-ce gets us up to 24.0.5, which is the same version as arch. So it’s possible to get there, just not out of the box. And by the time you start adding ppa’s to your distro, things stop being as stable.

tl;dr - If you need up to date software, debian is awful. It is rock solid, but often obsolete.

I use it for my server with the docker workarounds, but needing to do workarounds make it less fun. If I had to start over, I might pick something else like NixOS. I dunno. For “not going to crash” levels of stability, I can’t explicitly name anything better, but for “actually functions how i want it to” it’s definitely not at the top.

bisby,

Indeed. “Linux” now means “literally Linux, the kernel” and also “an operating system that uses Linux as the kernel”. Kind of like how people say they use “Windows” but they mean that they use “Windows 11”.

The only reason saying “GNU/Linux” helps is if you want to give credit to GNU. It doesn’t add clarity to anything. Which is warranted, but also, what if I forked GNU and relabeled it as linux-tools. I believe that’s within my right, isn’t it? To fork and copy things.

It’s kinda odd to be like “copyright is bad, the works should be free, and just pass around naturally!” … “but also make sure I get credit”

bisby,

Saying GNU/Linux does not give that message to 99% of people though. If I say that the SteamDeck actually runs on GNU/Linux to a normie gamer, they are more likely to be like “ok, that sounds confusing I’ll stick to xbox”. And anyone within the community already gets it. We all know the meme, we all get it. Semantics goes both ways. Sometimes you win hearts and minds, and sometimes you just annoy people who don’t care.

And in the name of semantics, “attribution” and “credit” are not the same. I’m obligated to say IceWeasel, or as I’ve taken to calling it, “The libre Firefox fork known as IceWeasel”… It’s important to call it by the full name every time, because Firefox is really the basis of 99.9% of the code in the repo. The repo gives full attribution to firefox and mozilla, but when we refer to it, we never actually give credit to the original.

And since we don’t need to call out the original if we fork something, if I fork GNU-utils and call it linux-OS-utils. And then build on my own distro, would that be a fully Linux OS? Even though its functionally and codewise identical to a “GNU/Linux” distro?

bisby,

I’m very unfamiliar with QT (and thus the python QT lib)…

But I had to change QTimer to import from QtCore, and Qpainter from QtGui for my local PyQT5 (from Arch repos).

This looks/works great but now I’m just a bit curious about why classes are in different places in different versions of pyqt5

bisby,

Awesome! Latest main works with no modifications needed now!

I’ve actually had a few times recently where I really wanted a color picker and just shrugged it off assuming it would be a hassle, or inconvenient to use. So thanks a ton for sharing.

  • All
  • Subscribed
  • Moderated
  • Favorites
  • random
  • uselessserver093
  • Food
  • aaaaaaacccccccce
  • test
  • CafeMeta
  • testmag
  • MUD
  • RhythmGameZone
  • RSS
  • dabs
  • KamenRider
  • TheResearchGuardian
  • KbinCafe
  • Socialism
  • oklahoma
  • SuperSentai
  • feritale
  • All magazines