• 3 Posts
  • 159 Comments
Joined 11 months ago
cake
Cake day: July 25th, 2023

help-circle




  • Bob@sh.itjust.workstoLinux@lemmy.mlTUXEDO on ARM is coming
    link
    fedilink
    arrow-up
    9
    arrow-down
    2
    ·
    edit-2
    6 days ago

    Mostly that they are generally made of cheap/very thin materials. They also kind of look like cheap Chromebooks (especially clevos, tongfang are better in this area). And it’s also the fact that these laptops aren’t really unique at all, they are mostly a logo swap with preselected components guaranteed to work with Linux. I’ve been using this Lenovo laptop that has a fantastic screen and an amazing CNC aluminum body, it works flawlessly and Linux support was never a consideration for them making this PC

    If I am buying a laptop i want it to be unique, because if it’s not then I’ll just buy it straight from China on clevos website for half the price. What I don’t like is this is basically drop shipping but less consumer hostile


  • In over 3 years of daily flatpak use (of multiple apps) I’ve never had a single reliability issue with flatpak, the only ones being caused by me because I was trying out settings in flatseal that the app didn’t like. On the flip side I’ve found native packages to be broken more often than not, with .Deb files sometimes just not working and throwing an error or something. Package managers are better for sure but I’ve had dependency issues that I have never experienced with flatpak.











  • Finally an option that is not just a dumb keyboard, this one has some local llms and local speech to text, so that’s pretty cool. Currently there’s no multilingual mode and I can’t find a way to adjust the height, but once these features are there I’ll happily switch.




  • I think the same, I often find that people overestimate their ability to write self documenting code and with the added mess of automatic formatters it often becomes hard to read and understand. In my department I am one of the few who actually writes comments and readmes that explains the reason behind some decisions. I am very junior, less than a year of experience, so maybe I will be able to better understand code that other people write in the future. But for the time being I write my documentation and my comments in a way that someone who doesn’t know anything about the project can understand, because I hate having to call coworkers because I can’t figure out how the project handles x and y (bear in mind that is also caused by Java “best practices” with 45 abstraction layers)