Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)ME
Posts
17
Comments
919
Joined
2 yr. ago

  • As a dev, you can just distribute a nixpkg with whatever build tool inside. That beats the current system of "native" packages where your software is repacked and then maintained by half a dozen teams for different distros that use different dependencies and update cadences.

    Bottles has gone as far as to demand its fedora package be removed and now shows a warning if you're not using the flatpak version because repackers just don't properly test all their software (how can they? there are thousands of apps in these repos!)

  • +1 for suggesting karl marx as a lorem ipsum user profile lmao.

    most of it is okay, but I do think it was a bit rude to basically call out a bunch of app devs for their icon styles, and suggest theyre updated for "modern styles", but other than that I'm not against their own repo wanting to have some polished metadata

  • I ran the diagnostics and they all came up clean, which I mentioned to Lenovo (who were pretty chill with getting the mobo replaced).

    It seems to happen more when the graphics are clocked lower, or transitioning from high power state to lower power states. That being said, I've so far had it work pretty good on KDE-Neon on Wayland. Haven't test X11 yet tho.

  • This is a big issue with Snap. It may be like Flatpak, allowing devs to set their own dependencies for ALL distros, but its poor uptake outside of Ubuntu's ecosystem means that it's no different to yet another distro repackaging system.

    Flatpak, or even Nixpkgs, are the future because they allow devs to have control over the distribution of their software. Snap being such a closed ecosystem in comparison only means it will replicate many of the problems we've found with traditional (re)packaging systems.

  • General memory-corruption artifacting, such as pink checker-boxes around elements that are animating on the desktop. Swapping from fullscreen games would sometimes lock the system with a white screen (visually) until I restarted GNOME.

    I've swapped over to KDE-Neon to see if Wayland might help, and it seems to have cleared up the artifacting but I can't be sure until I test some games.

    There's also a possibility that the System76 power daemon was causing issues. I noticed that artifacts disappear altogether if I'm running any kind of GPU test, and I've seen some suggest that the GPU was running at a too low frequency. Would make sense if the daemon was the cause as that's the other big change between Pop and KDE-Neon.

    I'll likely be back on Pop! when they bring out CosmicDE so I'll try again then, but it might be that I avoid it for now.

  • It's nice that we could see more rust in the kernel beyond drivers.

    Though looking at his code/documentation, it seems that the big win here is moreso giving higher time-slice values to applications that identify themselves as "interactive".

    This is a similar concept to what I've seen happen in MacOS, where even running unit tests for my work application doesn't bog down the rest of the system. In windows, however, a single heavy process can bring the whole system down to a crawl.

    Rust does have the benefit of being 1. safer on memory (though it uses unsafe blocks here) and 2. a lot easier to parse compared to (imo) archaic versions of C. Even this hobby project has some pretty impressive readability compared to some parts of the kernel that I've tried to read for the fun of it.

  • Unity has been getting better press because they mildly walked back a few of their policies. One prominent gamedev channel i saw (games from scratch i think?) did a video praising them for booting out ironsource execs (adware company unity bought a while back) from the company.

    And, like clockwork, Unity proves that it was never the plucky underdog that was going to take on the behemoths of unreal and (at the time of inception) cryengine. In fact, it feels like its more hostile to its users than either of its original competitors, that were once known for hostile and expensive features.

    And again, im gonna shill for godot. You're better off using FOSS for your tech stack primarily because of this kind of arbitrary behaviour that becomes standard once you're too big to be internally accountable.

  • Eh it failed in the most reddit way imaginable: Most of the users are too addicted to astroturf accounts posting heckin puppers and epic memes to organise a boycott beyond a few days. Reddit ownership knew how pathetic the "protest" was going to be from the outset and didn't even bother trying to disrupt it beyond nudging out a few of the remaining holdouts on subs too small to matter in the grand scheme.

    All the mods who thought they were irreplaceable just discovered their users are all the more happy to digest low quality slop moderated by amateurs who are more interested in the title than doing anything to protect the quality of said content.

    People are even relenting and PAYING for access to the API to use previously-free apps.