It has been a thing for longer that extensions are not allowed to make connections to the internet, unless it’s actually required for the functionality they advertise. And I believe, they have some rudimentary code scans in place to check for that. Besides that, there’s also their Recommended Extensions program, where they do thorough code reviews for a subset of available extensions.
They have the Recommended Extensions program, where they do that for a subset of the available extensions.
https://support.mozilla.org/en-US/kb/recommended-extensions-program
Yeah, HeliBoard or FlorisBoard would’ve been my recommendation. They’re very similar, though (and presumably share most code between themselves).
Multiple people have said that, yeah. But they also said that he did not particularly distance himself from the project, which is definitely something I would do, if I found out about this kind of backing.
Believe what you want, but Drew DeVault has more of a reputation than FUTO.
From a communication viewpoint, that is fair, but to my knowledge (from being a professional software developer), effectively any license that is not ‘open-source’ or ‘free’ is by definition proprietary.
Because those two terms describe licensing standards (the only established ones that I know of). Whereas I believe, “proprietary license” uses this meaning of proprietary:
Nonstandard and controlled by one particular organization.
So, they wrote that license themselves is the point. What it says in there is secondary in meaning.
This is so highly relevant because in legal disputes, there is certain license compatibilities which are known to be possible.
You can take a library licensed under the MIT license and use it in a project that uses the Apache-2.0 license and you’re perfectly fine. This is the foundation of why the open-source ecosystem exists at all.
But you cannot take the source code from FUTO and use it in a differently licensed project, because no legal precedents exist to support this. (I believe, the FUTO license also actively prohibits this in some way, but that’s beside the point.)
This has massive implications. Like, yeah, you can look at the code, but it is useless. If FUTO closes shop or enshittifies, you cannot fork their projects.
And because you cannot legally re-use their source code in other projects, likely no one looks at it in depth either.
Damn, I’ve had technological disagreements with Mr. DeVault in the past. Obviously, I did not assume those to mean I’d disagree with him on everything, but it still feels surreal to read an entire post where I’m fully on board with everything he writes (and appreciate all the info I did not know).
Cool to see that he’s fighting the good fight.
I’d argue that it’s Android’s DE for Linux.
Works fine for me. ¯\_( ᵔ ~ ᵔ )_/¯
Damn, I hadn’t seen the community name before reading the title and thought Microsoft was fixing up their filesystem. Of course, there’s more development happening on the non-Microsoft side.
There’s no way they actually checked that it works. It includes code for:
Verifying this would mean logging into several different desktop environments.
It’s also extremely fragile code, running external commands and filtering through various files. There just is no good API on Linux for querying whether the desktop environment is using a dark theme, so it’s doing absolutely inane shit that no sane developer would type out.
Because it’s a maintenance nightmare. Because they almost certainly don’t actually need to solve this. That’s software development 101, to not write code that you don’t actually need. But apparently some devs never got the memo that this is because of the maintenance cost, not because you weren’t able to generate the code up until now.
Ah, so you’ve scripted a whole bunch of stuff with YUM. Then you automatically have the downside that switching over could incur hours of work.
As much as the software developer in me wants to encourage you to use DNF (or an abstraction like pkcon) for newer scripts, in case they want to remove YUM one day, I get not wanting to deal with two separate tools.
In my head, switching over was trivial, i.e. just typing D, N, F instead of Y, U, M, because that was my experience when I switched over way back when I was still a freshly hatched penguin.
I’ve always liked Zypper (and if I remember correctly, DNF was also fine), purely because it feels sane in everything it does.
We love to make a religion out of them, but a package manager is ultimately just a secondary tool. It installs other tools, which are what you’re actually interested in using.
So, I shouldn’t need to learn a scramble of letters to achieve that. I shouldn’t need to think about refreshing the repository listing. The less I need to worry about instructing the package manager, the better.
There’s a section at the end where they’re mentioned.
No idea, if it has a TUI, but I feel like improved performance should be good enough of a reason to switch, if there are no downsides…
I couldn’t have imagined this playing out any other way. You’d need major changes to Windows to make it feel sensible here. And those are expensive as hell. If this were genuinely the horse that Microsoft’s investors are betting on, then I could have seen that kind of money being invested. But yeah, no, the horseshit they’re betting on is AI.
Isn’t that what always happens, though, that they only talk about changing things?
Oh man, I read that as “heaven no”, then as “heave-no” (like heave-ho), I even considered it might be some sort of Spanish. Did not make the connection with “hello” until I read the article.
Typically, touchpad gestures (particularly multi-touch gestures) will work better on Wayland, because it has libinput.
Title a dialog “Your ads, your choice” and then don’t give a choice to say no. You’d think their marketing department would realize how awful this looks…