• 0 Posts
  • 26 Comments
Joined 1 year ago
cake
Cake day: June 20th, 2023

help-circle



  • Kids finish school around 3 pm where I live. They have time to do their extracurricular activities (partially) during daytime even in the dead of winter. So of course it’s the mornings they find dreadful. If school finished around 5-6 pm I think they’d be miserable then as well.

    Speaking of which, I’m about to end my work day and the sun is setting right now. FML.


  • Yes it would. I, like most 21st century humans, wake up for work and have free time after work.

    In practice for my relatively northern latitude this means I get a little bit of daylight before work (except perhaps around december/january), but winter time is very specifically designed so that today the sun will set exactly 6 minutes before I end my work day.

    Were we to keep permanent DST I would get an hour of free time in the daylight today, and at least a little bit of light outside for all winter except perhaps for a month around December. As it stands, I do not get any free time in sunlight for 5 days a week for the entire duration of ST. The switch to ST means “bye-bye sun” and I hate it, I hate it, I hate it, I FUCKING HATE IT.

    The 24 hour clock is a made up construct. So are business hours. But if we already agreed to change one of these twice a year, can we make it so that it is not optimized to trap me inside for the entire duration of daytime???



  • Wait until you learn about debhelper.

    If you use a debian-based system, unless you have actively looked at the DH source, the one thing that built virtually every package on your system, you do not get to say anything about “bloat” or “KISS”.

    DH is a monstrous pile of perl scripts, only partially documented, with a core design that revolves around a spaghetti of complex defaults, unique syntax, and enough surprising side effects and crazy heuristics to spook even the most grizzled greybeards. The number of times I’ve had to look at the DH perl source to understand a (badly/un)documented behavior while packaging something is not insignificant.

    But when we replaced a bazillion bash scripts with a (admittedly opinionated but also stable and well documented) daemon suddenly the greybeards acted like Debian was going to collapse under the weight of its own complexity.




  • The main display that shows your speed,etc. randomly shutting down

    I know two people who had this exact issue with their new-gen Golf. First cause was the French language would crash the whole dash if you cycled the dashboard views (to my knowledge they never fixed the issue and the workaround is to set the car to English). Second cause was a malformed JPEG from a radio station would cause the dash to bootloop until you drove far enough from said radio station, which would allow the car to work long enough to disable that feature (IIRC).

    So yeah, QA is down the fucking drain with VW on their latest gen. They had a new CEO, and now a new one again I think? But the reputational damage has been done. Too bad, I really liked my '18 Polo.



  • It’s not as bad nowadays that apps yielded to GNOME’s bullshit. Back when GTK2 apps were still common… Urgh. Plenty of apps were broken without it for no good reason.

    I like opinionated UX - I use sway - but GNOME’s approach is incompatible with “general use” and only works (for now) because of canonical’s weight and ability to impose their vision as the only vision.

    Also they didn’t replace the tray with a better way to manage background apps, so they can suck a dick on the UX front.


  • The fucking system tray. Which literally every other DE and mainstream OS out there supports because some apps depend on it and break if it doesn’t exist.

    Last I checked GNOME devs said “no, we will never support it, because we’ve DePRecATeD the tray in GTK”.

    It’s functionality so basic I have 3-6 apps which depend on it at any time on my work machine. Anyone saying it doesn’t fall under “basic functionality” is either a GNOME dev or a troll.




  • You don’t need a data plan to call emergency services. Any protocol-compatible device can dial 911/112/etc. for free.

    This is why in remote areas your phone may say “Emergency Calls Only”. Your carrier isn’t available, but someone else’s is and they are legally obligated to route emergency calls.

    Of course if your car has a modem and a computer, adding a data plan isn’t a huge leap. But it’s a recurring expense and plenty of cars sold today do not have internet connectivity, at least on the cheaper side.




  • “Color terminal” isn’t a thing. Applications can choose to output ANSI escape codes which most terminal emulators will render as color changes. Whether and which colors get used depends on the value of $TERM, which informs the application of the capabilities of the terminal emulator.

    So if your remote servers don’t have color, either $TERM isn’t being set or its value is unknown to the server. Most modern terminal emulators support at least the same escape codes as xterm-256color though so you can always try to export that.