rotopenguin

joined 2 years ago
[–] rotopenguin 9 points 2 years ago

Lol I just leveled up to "stick that spits out dozens of tiny rocks very fast"

[–] rotopenguin 11 points 2 years ago (2 children)

It's tricky enough getting hardware video encode to work on Linux with "this is just an Intel IGP, the exact same thing as every other Intel IGP". Decode can even be tricky at times. I am very pessimistic about getting video editing software working on a system as far off the beaten path as a Snapdragon.

If you stick with more mainline hardware, you have fallback positions like "use linux Davinci" or "dual boot Windows and use one of the gazillion tools there", or "MacOS has its own cavalcade of media tools".

[–] rotopenguin 6 points 2 years ago* (last edited 2 years ago)

*chuckling*: Afghanistan may be the graveyard of other empires, but I'm built different

[–] rotopenguin 2 points 2 years ago* (last edited 2 years ago) (1 children)

It can, but it's not trivial to set up. First you have to reformat/convert to btrfs, then you have to chattr everything, and defrag to do a compression pass on the existing stuff. And after all that, Steam does every download and patch with a preallocate that blocks out the online compression, so you have to subvol and anti-cow its downloading folder to defeat that.

[–] rotopenguin 50 points 2 years ago

Nah m8, the Wojak looks too human to be him

[–] rotopenguin 5 points 2 years ago

That's what makes it Covid-safe.

[–] rotopenguin 2 points 2 years ago

And the driver is stuffed if the hardware decides to have an unrecoverable issue.

(I'm looking at you, Intel GuC. You dumb little bastard.)

[–] rotopenguin 6 points 2 years ago

There is a proposal to consider making a Wayland extension where programs can sit around and re-attach to a fresh, non-deaded display server. KDE is much closer to having a working version.

[–] rotopenguin 9 points 2 years ago (1 children)

My main problem with Flatpak is that it hands temporary /var/run/1000 file links to programs instead of real filenames. That would almost be bearable, if Flatpak also took responsibility for keeping those links from breaking sometime after your next reboot.

If I say "here is a path that an app is allowed to use", flatpak should just allow an open() in there to work. It should not lie about the name of files in there. An app should be able to open a file there, remember that name, and count on being able to access it again in the future.

Other than that, Flatpaks are the bees knees. I love finding something I want to do, finding a solution in the flatpak store, and click-click I'm already doing shit. Finding Windows software is absolute garbage next to this.

[–] rotopenguin 1 points 2 years ago

Yeah, you're probably right. I'm thinking in terms of "not a raid, no redundant copies available" scrub, where the main output would be a sanity check of data checksums.

[–] rotopenguin 1 points 2 years ago* (last edited 2 years ago)

Then use openscad. It's way easier 😉

(It is quite funny to see this post get thumbs-up from the "oh openscad sounds neat, I'll have to check that out" crowd, and later see the thumbs-down rolling around like "nope. nope. Did not like that one bit.")

[–] rotopenguin 6 points 2 years ago* (last edited 2 years ago)

I've seen an Apple battery or two puff up at that age. Highly recommend getting that old battery swapped out.

view more: ‹ prev next ›