worse? If this means that they refocus on things that matter then I consider this better.
worse? If this means that they refocus on things that matter then I consider this better.
verso is a seperate project, it’s not built in, servo’s built in browser is more of a basic shell for usability and testing stuff.
EDIT: My bad, no glasses, misread on for in, there is also moto https://github.com/moto-browser/moto
I am actually really glad to see this happen, Mozilla needs a massive refocus on what actually matters (Firefox, Thunderbird, new tech etc).
there was once a time when mozilla was at the fore front of tech development and they were churning out extremely cool tech one after the other. Servo, DeepSpeech, Firefox reality (wolvic is the successor in case anyone was wondering), a TV browser (Why did they have to kill this of all things off T.T) and others.
I want to see mozilla put more focus, and more importantly, a larger portion of the money they receive on actually doing things.
personally I am not super interested In this, vulkan venus is going to be a lot more portable which is key for me.
The War in Ukraine Was Provoked—and Why That Matters to Achieve Peace
The shooting war in Ukraine began with Yanukovych’s overthrow nine years ago, not in February 2022 as the U.S. government, NATO, and the G7 leaders would have us believe.
So many people forget that the Ukrainian Russian conflict never really ended, the idea that it was an unprovoked invasion is absurd, (and no, before someone decides to make a braindead comment, provoked does not mean justified.) There have been many leaked videos pre-invasion of violence towards both sides, and neither side made a proper effort to actually quell it, only surface level bullshit inorder to take the "moral ground:
Nazi germany came into being a thing because post great war was massively hard on germans in large part to the treaty of versailles completely crippling germany’s economy.
ofc there were other factors like the massive propaganda machine, Germany was effectively reduced to a slave state dealt a massive blow to the pride of the german populace which was fairly easy to turn young men militant alone, even disregarding the disastrous effects to the German economy.
I am quite disappointed at the lack of transparency regarding this.
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.
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
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
Firefox is understaffed, servo was canned, deepspeech was canned, firefox reality was canned, firefox for android TVs was canned, send was canned, the upstream project which the translate feature is based on (bergamot) has been extremely inactive and many more.
each one of these projects was/is “important” in some way, and while there are alternatives now or have been picked up by various third parties, each one had a lot of untapped potential, and lets take a look at the projects alternatives or forks current state.
servo: was picked up by igalia, and is massively far behind, It still has a lot of potential, and progress is quick for what it is, but this is a real embeddable alternative to chrome. Not viable yet, and likely wont be for another year or two.
Deepspeech: Coqui is dead, existing speech to text stuff is all either proprietary or extremely low quality. Only recently have we seen some progress due to speech to speech AI (AI voice replication). Still largely unusable. Some promising projects have cropped up but none are viable yet.
Firefox reality: Wolvic took over, it’s in the process of being ported to chromium.
Firefox for android TV: No alternatives even exist, you have TVBro and Vitabrowser are all just barely usable. and they rely on webview, a geckoview browser https://github.com/threethan/LightningBrowser which isn’t really usable.
Send: This is the one fork that is actually flourishing. This is really a nifty service at least.