drwankingstein @ drwankingstein @lemmy.dbzer0.com

Posts

0

Comments

465

Joined

2 yr. ago

will do when I find the time. Didn't know it was in that stage yet. Don't like spamming issue tickets for new projects that haven't had time to spread its legs yet.

Gnome is heavy to use, and buggy, lots of people like the design of gnome, but not the perf hit. It will be nice to use apps that both don't suck, and fit our general aesthetic

Nice, was able to get cosmic-edit and cosmic-term working on windows even. cosmic-files crashes out with a windows memory error, the crash doesn't happen within cosmic-files though so I can't get a backtrace. It does seem to work well enough through WSL2 though

a capitalist funded anarcho-comunist ecosystem, ironic

A couple other things, you generally want to do pixel format conversion before the codec, is specified. You should be able to get satisfactory results with ffmpeg -i input.mpv -pix_fmt yuv420p -c:v libx264 -preset medium -crf 24 -c:a aac output.mp4 Play with preset a bit since that is where your Quality/Compression : Speed ratio comes in, CRF is the quality it handles. So you set CRF for a ballpark quality you want, then change the preset, slower = higher compression, faster = lower compression.

you can find more info here https://trac.ffmpeg.org/wiki/Encode/H.264#a2.Chooseapresetandtune but generally you don't need to muck about with profiles or tunes or anything else

I think it's worth keeping in mind since when people ask for something, they generally want something specific. in this case they asked for a distro, so there is a non insiginificant chance they wanted a "generally agreed upon distro"

you will likely find that most people will disagree with that, the general consensus of a "Linux distro" is that gnu/linux stuff. Personally I would consider it distros in which the apps would mostly use the general linux runtime stacks since musl based distros I would still consider a general linux distro. Android uses it's own distinct runtime, for the vast majority of usage, and although using things like termux we can get close, how android is setup it lacks a good chunk of things that can only be resolved with a chroot/proot

using openh264... well that's a choice. I would recommend to everyone that they use x264 whenever possible, and make sure to specify output crf and likely preset when you fo

one of the issues I have with mobile linux is flutter has some really good apps, but when you try to use them on linux the performance plummets, this makes a whole slew of great touch primary applications unusable.

this article was pretty hard to read, but I greatly disagree with android having bad UX, maybe for some users but to me android's UX is pretty great

While I agree that it is the best tablet experience, I think that's strething the definition of a distro pretty hard lol

each one of them has issues, I cant in good conscious recommend any atm

considering android allows you to actively change the default assistant it won't be a problem, we already have plenty of apps that use overlays that are foss so that's not an issue either, so I really have no idea what you think would be locked down here.

dicio is just kind of a clunky app

I actually really like Chrome OS myself. For the people around me who are less tech literate, Chrome OS is actually great. It's quite easy to support. It's fast, and it's got a really good ecosystem now thanks to all the integrations.

Year of the chromeOS desktop maybe, may faith is low

while I do agree that x11 could be better in that regard, having the baseline critical features met matter a lot more then security for me.

I personally really like wayland, I just wish it actually was properly usable in all my use cases

Man incapable of reading rules gets angry when punished for violating rules

I didnt even remotely imply that x11 doesn't have issues, so im not sure why that was brought up. The goal is to make wayland an acceptable and universal replacement, Everyone knows x11 is dying but wayland isnt ready to replace it yet

Things like window embedding, the wayland way is for each app to have it's own embedded compositor. Wayland has no support for things like overlays/always on top (Useful for OSKs PR has been made but like all wayland things, we might not get it for another couple years, or perhaps never), currently missing support for reading other window states (PR made for this as well, but again, who knows how long it will take), Still no support for window positioning (again PR made), Emulated input events (libei is not universally supported) And these are just the ones off the top of my head, There were others but I cant think of them ATM

I really don't like nate's take here. IMO it's really not that good, Wayland is still outright lacking features, even when using the craptastic xdg portals junk

so I don’t know if they run their own apps, or if they run Linux programs. If they run Linux programs, then it’s just a case of finding one that controls your specific camera, and has the controls that you want.

we can run linux desktop, linux mobile or android apps, but camera support in waydroid is broken for a while when using v4l2

the general Idea I am getting from this would be something where the phone itself could be swapped out