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

help-circle

  • Because batteries are a point of tension in the adoption of some electricity-centric techs. Electricity production can be done in many different ways already (unless you suddenly decide to 100x the demand for shit and giggles), but a lot of applications requires batteries, which makes them some sort of choke point for adoption. Making them better, more accessible, cheaper, more friendly on the environment ease that.

    The comparison is also on one end of the world focusing on the dying down side of things, while the other end is (allegedly) looking forward.

    That’s why they’re compared.






  • When it gets to the point where it does work to produce usable documentation, without extraneous content, with no mistakes, can be checked quickly, and it is faster to generate + check than to write it, maybe. Assuming a stellar history of being correct from the tool.

    As it is right now, once you reach the point where you actually need proper documentation to be written to keep things maintainable, these tools have low accuracy, lots of issues, and using them takes longer than it takes a competent person to just write/update whatever needs to be.







  • Technically, all the boot options were on the same drive (same EFI partition, on the disk that was initially used for years by windows), but for some reason, the motherboard decided “nope, there’s no bootloader there”.

    I ended up repartitioning the “first” drive seen by the bios to make a 100MB partition at the beginning, named it “EFI system partition”, copied all the content of the old one from the other drive, and nuked the actual windows install in the process (not the boot entry though). Now all is good… I hope :D




  • Might be off topic, but does anyone else dread the outcome of their Linux system after an update?

    Not really. I don’t really worry about that on most of my system. There is ONE computer where an update is a source of stress, and that’s my main gaming computer where I had to setup dualbooting with windows. I learned the hard way that my motherboard implementation of UEFI kinda want windows to be there, otherwise it’s very picky into which disk is parsed for EFI boot entries. But beyond that, nah. Laptop, desktop, company servers… just roll the update/upgrade, and the dist-upgrade when needed, fix the updated configs (for servers) and it’s good to go. Been this way for the last decade or so.

    Worthy of note, I’m on ubuntu LTS (24.04 for now) or Debian stable (for servers), so not exactly outdated (I have the latest nvidia drivers…) but not bleeding edge either. I probably avoid a lot of issues this way.


  • I have no idea when it happened, but there’s a mechanism in place to download updates but only install them on reboot, kinda similar to windows, but when you want instead of when it want. It’s kinda the best of both world : updates are quick to install, downloaded in the background, and no workflow interruption.




  • Yeah. I’m on a relatively old build with DDR4, but still a decent processor and GPU. So far gaming have not been an issue with whatever I’m throwing at it. Not much in the way of loading times, and no real problem with the size of it. Some less game-y stuff, like video transcoding and 3D renders, also fine. And while I can see those improving somewhat with DDR5, I’m not sure it’s the actual bottleneck. And gaming won’t be much better with it… I mean seriously, moving loading times from 3 seconds to 2? I don’t really care.

    The real issue will be when things starts to break down, as hardware do over time. It’s not that I want to replace the hardware if there’s no pressure from the software side, but I will have to if RAM goes bad, or motherboard decide to not power up.