• 0 Posts
  • 52 Comments
Joined 8 months ago
cake
Cake day: April 3rd, 2024

help-circle
  • Is your meme about oil rig explosions related to reposts you’re making this weekend?

    ○︎ No, it’s not related to weekend reposts
    ◉︎ I’ll repost this both on weekend and weekday
    ○︎ Yes, both for this and future weekends
    ○︎ Yes, I’ll repost this on every future weekeend
    ○︎ Yes, I’ll repost this purely on this weekend


  • Nah, I’m thinking of sodium-ion batteries. That’s 1990s tech and is currently in use for grid storage. Several manufacturers are currently bringing car-ready Na-ion batteries to market and there seems to be one production car using them in China (a version of the JMEV EV3, which I hav enever heard about before).

    Now, Na-ion is still less mature than Li-ion and that Chinese car gets about 17% less range compared do the Li-ion version.






  • Flatpak has its benefits, but there are tradeoffs as well. I think it makes a lot of sense for proprietary software.

    For everything else I do prefer native packages since they have fewer issues with interop. The space efficiency isn’t even that important to me; even if space issues should arise, those are relatively easy to work around. But if your password manager can’t talk to your browser because the security model has no solution for safe arbitrary IPC, you’re SOL.



  • To be fair, it had its moments. Windows 95 was a pretty big step forwards and the alternative was OS/2 Warp, which has some nice features but was from IBM, who were still dreaming of replacing the PC with a vertically-integrated home computer again.

    Windows 2000 (or XP starting with SP2) was also solid. 7 was alright. None of those had too much bullshit bundled with them.

    Everything since Windows 8 has been some flavor of shitty, though.



  • The software development industry version of this is “we really need to fix that soon but it’s beyond the scope of this PBI”.

    “Soon” is a shorthand for “we’ll put this on the backlog and never pull it into a sprint until it blows up in our faces, at which time we will gripe about how nobody bothered to fix it earlier”.


  • Jesus_666@lemmy.worldto196@lemmy.blahaj.zoneNocturnal rule
    link
    fedilink
    English
    arrow-up
    58
    ·
    20 days ago

    We know that people have different chronotypes. We even know that most people of working age aren’t really morning people. Unfortunately, our business world assumes a standard circadian rhythm and is structured around getting up early because people needed to use every bit of daylight way back when. So that sucks, especially if you’re an evening or even night person.





  • Jesus_666@lemmy.worldtoLinux@lemmy.ml*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    2
    ·
    1 month ago

    Oh yeah, the equation completely changes for the cloud. I’m only familiar with local usage where you can’t easily scale out of your resource constraints (and into budgetary ones). It’s certainly easier to pivot to a different vendor/ecosystem locally.

    By the way, AMD does have one additional edge locally: They tend to put more RAM into consumer GPUs at a comparable price point – for example, the 7900 XTX competes with the 4080 on price but has as much memory as a 4090. In systems with one or few GPUs (like a hobbyist mixed-use machine) those few extra gigabytes can make a real difference. Of course this leads to a trade-off between Nvidia’s superior speed and AMD’s superior capacity.


  • Jesus_666@lemmy.worldtoLinux@lemmy.ml*Permanently Deleted*
    link
    fedilink
    English
    arrow-up
    8
    ·
    1 month ago

    These days ROCm support is more common than a few years ago so you’re no longer entirely dependent on CUDA for machine learning. (Although I wish fewer tools required non-CUDA users to manually install Torch in their venv because the auto-installer assumes CUDA. At least take a parameter or something if you don’t want to implement autodetection.)

    Nvidia’s Linux drivers generally are a bit behind AMD’s; e.g. driver versions before 555 tended not to play well with Wayland.

    Also, Nvidia’s drivers tend not to give any meaningful information in case of a problem. There’s typically just an error code for “the driver has crashed”, no matter what reason it crashed for.

    Personal anecdote for the last one: I had a wonky 4080 and tracing the problem to the card took months because the log (both on Linux and Windows) didn’t contain error information beyond “something bad happened” and the behavior had dozens of possible causes, ranging from “the 4080 is unstable if you use XMP on some mainboards” over “some BIOS setting might need to be changed” and “sometimes the card doesn’t like a specific CPU/PSU/RAM/mainboard” to “it’s a manufacturing defect”.

    Sure, manufacturing defects can happen to anyone; I can’t fault Nvidia for that. But the combination of useless logs and 4000-series cards having so many things they can possibly (but rarely) get hung up on made error diagnosis incredibly painful. I finally just bought a 7900 XTX instead. It’s slower but I like the driver better.