Canadian software engineer living in Europe.

  • 5 Posts
  • 194 Comments
Joined 3 years ago
cake
Cake day: June 7th, 2023

help-circle


  • This is nowhere near the average Debian update experience. Debian is favoured precisely for its stability and simplicity, so if youre getting stuff like this, it’s far from average.

    Those errors look like file corruption. Maybe they were partially downloaded or written to a flakey disk, it’s hard to say. I’d also echo the other comment or that Kali (and honestly Debian) are not well suited for gaming due to the distro preference for Freely-licenced software and favouring stability vs quick releases.

    It’s fine if you want to experiment and “swim against the current” to do a thing with a tool for which it’s not designed, but turn around and complain as if this is normal behaviour is either dishonest or outs you as someone who doesn’t have the experience required to make such a statement.




  • Your math is waaaaay off. Let me help you.:

    Let’s assume that you commute a rather conservative distance of just 25mi to work. That’s 50mi/day, 5 days/wk, plus let’s say half that over the weekend. Assuming an (again, generous) fuel efficiency for your truck at 25mpg, given a ballpark 300mi/week, that’s 12 gallons of fuel/week. The current average price of gas in the US is a remarkably low $3.071, and that adds up to $36.85/week.

    Now consider the costs of maintenance. If you’ve really had zero problems in the last 20 years on a pickup truck (honestly this is far from average), you likely did an oil change every 3 months at the very least. These days it’ll run you about $100.

    In terms of insurance, I asked this site for the average cost of insuring a Toyota pickup truck for one year: $1937. Let’s be grossly optimistic and pretend that those rates will never go up.

    Initial cost: (Provided)                    = 11000.00
    Fuel costs: (50 × 6 ÷ 25 × 3.071 × 52 × 20) = 38326.08
    Oil changes: ($100 × 4 × 20)                =  8000.00
    Insurance: (1937 × 20)                      = 38740.00
    Parking:                                    = ?
    ------------------------------------------------------
    Total                                         96066.08
    

    Excluding the cost of parking, the purchase of your miracle never-needs-repair truck if purchased today would be roughly $100,000. Note also how very conservative these values are. It’s entirely possible that your real costs are well above what I’ve stated here.

    The total cost of the rental was $1000 plus fuel costs, so using our above figures, that’s a grand total of $1042.99 assuming you drove it roughly 50mi/day for all 7 days of the week. That’s assuming that you don’t opt for the much lower rates that appear to be available to you in the area of $250 - $350/week.

    So, if you didn’t own a car and instead only rented one when you needed to “move a couch”, you would save just over $95,000. In other words, your insistence that you absolutely must own your own vehicle has cost you the equivalent of a downpayment on a house.






  • The bit of information you’re missing is that du aggregates the size of all subfolders, so when you say du /, you’re saying: “how much stuff is in / and everything under it?”

    If you’re sticking with du, then you’ll need to traverse your folders, working downward until you find the culprit folder:

    $ du /*
    (Note which folder looks the biggest)
    $ du /home/*
    (If /home looks the biggest)
    

    … and so on.

    The trouble with this method however is that * won’t include folders with a . in front, which is often the culprit: .cache, .local/share, etc. For that, you can do:

    $ du /home/.*
    

    Which should do the job I think.

    If you’ve got a GUI though, things get a lot easier 'cause you have access to GNOME Disk Usage Analyzer which will draw you a fancy tree graph of your filesystem state all the way down to the smallest folder. It’s pretty handy.



  • Daniel Quinn@lemmy.catoLinux@lemmy.mlWhy?
    link
    fedilink
    English
    arrow-up
    2
    ·
    2 months ago

    I was a Windows user as a kid in the 80s & 90s doing pirate installs of 3.11 and later 95 for friends and family. I got into “computers” early and was pretty dedicated to the “Windows is the best!” camp from a young age. I had a friend who was a dedicated Mac user though, and she was bringing me around. The idea of a more-stable, virus-free desktop experience was pretty compelling.

    That all changed when I went to school and had access to a proper “Mac lab” though. Those motherfuckers crashed multiple times an hour, and took the whole OS with them when they did it. What really got to me though was the little “DAAAAAAAAAAA!” noise it would make when you had to hard reboot it. It was as if it was celebrating its inadequacy and expected you to participate… every time it fucked you over and erased your work.

    So yeah, Macs were out.

    I hadn’t even heard of Linux in 2000 when I first discovered the GPL, which (for some reason) I conflated with GNOME. I guess I thought that GNOME was a new OS based on what I could only describe as communist licensing. I loved the idea, but was intimidated by the “ix” in the name. “Ix” meant “Unix” to me, and Unix was using Pine to check email, so not a real computer as far as I was concerned.

    It wasn’t until 2000 that I joined a video game company called “Moshpit Entertainment” that I tried it. You see, the CEO, CTO, and majority of tech people at Moshpit were huge Linux nerds and they indoctrinated me into their cult. I started with SuSe (their favourite), then RedHat, then used Gentoo for 10 years before switching to Arch for another 10+.

    TL;DR: Anticapitalism and FOSS cultists lead me into the light.





  • Daniel Quinn@lemmy.catoProgrammer Humor@lemmy.mlWebp
    link
    fedilink
    English
    arrow-up
    3
    ·
    3 months ago

    That’s exactly the reasoning Google has followed with its development and promotion of webp. Unfortunately, whether the website cares or not, CO₂ emissions are markedly higher due to increased client energy consumption, and that does directly affect you, so it’s worth considering the implications of using webp in a popular site.


  • Daniel Quinn@lemmy.catoProgrammer Humor@lemmy.mlWebp
    link
    fedilink
    English
    arrow-up
    15
    ·
    3 months ago

    Webp is pretty great actually. Supporting a 32bit alpha channel means I’ve actually managed to reduce file sizes of what were formerly PNGs by something like 80%, which drastically improved performance (and the size of my project). I don’t get where the complaint of image quality came from either, as it seems to perform better than JPEG at the same file size.

    The worst part is that you missed the real problem with the format: the CPU overhead (and therefore the energy cost) of handling the file. A high-traffic site can dramatically increase the energy required for the images processed by the thousands/millions of clients in a single day, which places a drain on the grid and emits more CO₂ (yes, this is really a thing that people measure now).

    Basically Google invented the format to externalise their costs. Now, rather than footing the bill for bigger datacentres and greater bandwidth, they made everyone else pay for decompression.