• 0 Posts
  • 12 Comments
Joined 3 years ago
cake
Cake day: June 12th, 2023

help-circle

  • Unrelated, but I just took apart my old IBM thinkpad from 2003/2004 to clean it up and get all nice and pretty for it’s last few years of updates. I also did my newer-ish HP laptop from 2016 at the same time.

    The thinkpad was just beautifully laid out, with thought put into the placement of vents, heat sinks, heat generating components, alternative air pathways if the entire bottom was blocked, easy maintenance of components, etc.

    The HP was …not. The weakest ass heat sink I’ve ever seen, miles away from the processor (no wonder it sounded like a wind tunnel when playing a youtube video). One intake vent where your thigh would be if in your lap and the exhaust right where your knee would be. Extra bonus was the placement of the CPU (running usually 80c+) is right above your junk, the vent being offset from the processor a smidge.

    Granted I’m comparing enterprise vs consumer laptop in the days when there was a massive difference in quality between the two, but damn, this experience has me decided (again) that internal layout and design is just as important as specs, even more so if you need more powerful components.





  • I just had an issue with the vscodium flatpak, been using it for two months with no issue in an online course, got to learning GUIs, import module, doesn’t exist. I couldn’t figure out why it wasn’t there, installed three different python versions of it three different ways, still nothing. Couldn’t even get vscodium to point to a different interpreter that I knew was there (yet it doesn’t say it’s not there, just that some things won’t work). Still nothing. Three hours later, after trying everything I could think of, I realized that it was because I installed the flatpak version when it clicked that it worked in Geany and I didn’t have python 3.13 in my repos, yet that was the only one I could see in vscodium.



  • Our work tried to push thin clients. It didn’t go well because they did not invest in the back end and infrastructure to do it. Constantly unable to reach the server, often bogged down because three people were running heavy applications where they should have had a dedicated machine, the storage server was sometimes a microwave link away that would nearly die if it was raining.

    I’m usually at three different workstations throughout the day, sometimes there’s even three others that I might end up at, and it was so nice to just connect to my instance and continue, nothing’s worse than opening up an excel you worked on for two hours at a workstation five minutes from your current one and it’s “locked by another user” and you don’t remember what all you might have changed from your last save.

    I do not do any resource intensive work that isn’t on a dedicated machine, so I would be perfect for thin client use. But there were so many little things they didn’t or couldn’t do that built up to it being a useless endeavor.


  • I’m mostly bottlenecked by IO performance and network speeds. So in order to happily take advantage of a blazing fast machine I’d need to do some upgrades everywhere else. As long as I don’t get one, I won’t feel the need to update. I got real close the other day transferring 1.5 TB of data to a backup drive over 1Gb after doing some file server to file server shenanigans over 2.4ghz wifi with a 32GB filesystem image.

    FYI, decompressing an image on a fileserver back onto the server through a laptop, then writing the decompressed image on that server to a disk connected to said laptop, all over 2.4ghz WiFi, is a monumentally stupid way to do things. Many circumstances were involved, the biggest of which in this escapade was me unwilling to walk across the house because of… I don’t know, reasons. The second biggest being I had already pressed enter, so screw restarting the process in a way that would be 4x or more faster, I was already 10% done.





  • I learned this relatively quickly running my own server with the intention of my family also using it. Data on a separate drive, backed up regularly and automatically. System on it’s own drive, dd’d when it’s in it’s final state and backed up before I screw around any deeper than trying out a new container. I can bring my server back up in however long it takes to transfer data.