I have a 12vdc direct power USBC charger for my tablet. This will totally fry any normal USBC device it touches.
can't say I have experienced that. I use a myriad of modern but lower end systems and stuff like dinit still uses less resources and is in turn better for the speed and responsiveness of my systems
this is pretty much how it works in some cases, you need to port from one protocol to another, or to a different system altogether.
I'm pretty sure everyone has settled by now, Personally I hate systemd. It's slow, relatively resource intensive, poorly designed in many aspects.
but as an init and service manager it's the best. Though I do have to say dinit does get pretty close for me now.
I personally use Arch on my desktop and artix on my laptop. I want Systemd to die just as much as the next Systemd hater, but unfortunately I don't believe we have anything better yet.
that's just the thing, This is again, more fragmentation, Some compositors support always on top, some don't, you choose x protocol for your app, and now your app works great on sway, but not on KDE or gnome, or it works great on gnome and not kde or sway etc. As an app developer the situation is a bloody joke. My current stance is "just use xwayland because wayland will never be suitable" and thankfully with cosmic and kde both supporting "don't scale xwayland" this seems to work well.
EDIT: they also make enough deviances from the upstream protocols that this can't really be considered a "experimental branch"
EX: https://github.com/misyltoad/frog-protocols/blob/main/frog-protocols/frog-color-management-v1.xml vs https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/14/diffs
Yay, another set of protocols that will just lead to more and more fragmentation.
You do acknowledge one issue with Wayland, probably the biggest issue with Wayland, but then fail to acknowledge the second biggest issue with Wayland being fragmentation.
Solve one issue by making another issue worse.
Nine times out of ten, running chown on Android is an astronomically bad idea. 10 times of 10, what you're trying to do right now, is an astronomically bad idea.
What is it you are trying to do? Or rather, why?
The best YouTube TV app for desktops is YouTube TV.
Look up PS4 Pro Leanback UserAgent and I recommend using that with Chrome because Firefox has a little bit of bugs. If you use it as a web app it works pretty well. The one caveat is you cannot exit out of it without enabling a developer flying in Chrome, without that flag you need to use alt + f4.
You want to use a web app or kiosk mode, specifically because resolution that you get in video is determined by the window size at startup, so if you have a 4K display, it needs to be full screen at start or else you will not get 4K video. Playback, you'll only get 1440p.
Otherwise, just full screen it, then refresh.
I personally have found that the kodi plugin is quite frankly not very good.
Cromite. It's easily the fastest browser i've used. Good baked in adblock is all I really need, and the increased performance and compatibility vs firefox is nice.
yeah, that could indeed happen I suppose, didn't think of that. Though I wonder if because of EME, an alternative drm solution could be viably implemented.
this has been a bit of a meme, but if you wanted to look at XL as extra large, then that could refer to the max resolution which is far great. I've seen people refere to it as "extra long-term" but I think the real reason is they just wanted to fuck with us
I don't think this is a thing just yet. at least not that I have noticed
like what? I can kinda understand them not cooperating but how on earth could they lock them out of features?
ehh... not really, the amount of generated data you can get by snopping on LLM traffic is going to far out weigh the costs of running LLMs
I don't even think this is the case, google does a lot pretty much everywhere. one example is one of the things they are pushing for is locally run AI (gemini, stable diffusion etc.) to run on your gpu via webgpu instead of needing to use cloud services, which is obviously privacy friendly for a myriad of reasons, in fact, we now have multiple implementations of LLMs that run locally in browser on webgpu, and even a stable diffusion implementation (never got it to work though since my most beefy gpu is an arc a380 with 6gb of ram)
they do other stuff too, but with the recent craze push for AI, I think this is probably the most relevant.
this is from the google research team, they contribute a LOT to many foss projects. Google is not a monolith, each team is made of often very different folk, who have very different goals
I remeber testing parrot a few years ago, it was quite nice back when I tested it, had some real cringe marketing back then, way worse then it has now by quick glance, that being said, it had some real good OOB configs for security stuff and some neat tools. wouldn't mind trying it again sometime when I find the time.
color management is actually super hard to do, so making sure it's done right is very important, so this is one of the few times it actually makes sense. I mean, just take a look at windows, it still looks like shit over there.
for the semantically inquisitive folk.
It's worth noting if you are using this on an arm device, this isn't a "virtualization VM" any more, as you are using the emulator backend, so this is far closer to a traditional emulator then anything else.
While the term virtual machine is extremely poorly defined, it could still apply.
also TCG is as slow as molasses, it's a good demo, not actually usable for much, at least unless it's a super beefy phone.