Because I like the 2-clause BSD license. I am not a fan of βcopyleftβ or forcing obligations on people in general. I want my software to be available for anyone who wants to use it.
Spectacle8011
joined 1 year ago
The reasons are made clear on their roadmap.
The GTK3 port is done, and now they need to finalize the new extension API and improve their color space support (particularly CMYK). It would be nice if Wayland had a color management protocol extension standardized by then, but I don't think it's a blocker.
Cheers. I use Krita myself, but I've heard people say "Krita is terrible; try FireAlpaca." I think that might be because it has performance issues on other operating systems; I'm not in a position to test. It's good to hear Krita is basically ahead on all fronts except learning curve. Nonetheless, it's nice to see a Linux version. FireAlpaca advertises a Dark Mode, but I'm guessing it's a paid-only feature.
I've heard some artists prefer FireAlpaca to Krita. Is there anything it does better than Krita?
I don't doubt it, but this is a good place to start.
This claim has interesting phrasing:
Adding X11 sandboxing via a nested X11 server, such as Xpra, would not be difficult, but Flatpak developers refuse to acknowledge this and continue to claim, "X11 is impossible to secure".
If you look at the GNOME post, you'll see they haven't argued against including a nested X server at all:
Now that the basics are working itβs time to start looking at how to create a real sandbox. This is going to require a lot of changes to the Linux stack. For instance, we have to use Wayland instead of X11, because X11 is impossible to secure.
I'm not saying they haven't refused to acknowledge this elsewhere, but it's strange to point to this blog post which acknowledges that the sandbox is very much a work-in-progress and agrees with Madaidan that X11 is hard to secure.
Does Xpra provide better sandboxing than XWayland? If not, I think the Flatpak developer's solution to this is: just use Wayland. And obviously, there's plenty of room to improve with the permissions Flatpak does offer.
I did some searching on the Flatpak Github for issues and found that you can actually use Xpra with Flatpak, and the answer is "just use Wayland":
This is also concerning:
As odd as this may sound, you should not enable (blind) unattended updates of Flatpak packages. If you or a Flatpak frontend (app store) simply executes
flatpak update -y, Flatpaks will be automatically granted any new permissions declared upstream without notifying you. Using automatic update with GNOME Software is fine, as it does not automatically update Flatpaks with permission changes and notifies the user instead.
Source: https://privsec.dev/posts/linux/desktop-linux-hardening/#flatpak
It's great that GNOME Software notifies you when permissions change! I don't use Flatpak enough to know, but I hope flatpak update notifies you too if you don't use the -y option.
Aussies tend to be quite direct. It's basically our natural state. I get how it can be perceived as hostile, but I don't actually think Brodie is very abrasive. He seems like a pretty relaxed guy.
I use both GNOME and KDE. I do have a system tray, but it's for a single program: fcitx-mozc. If I didn't need to build ibus-mozc from source, I would just use that. iBus IMEs get their own spot in the top right without needing appindicators. That being said, I don't need the system tray either as I can just switch between Japanese and English with CTRL+SPACE. But it's nice to have some kind of constant indication what IME I'm using.
On the subject of a dock, though, I love the way GNOME completely separates it from the workspace. It just takes up space and I don't have any utility for it. Windows and macOS only allow you to hide the dock; not remove it completely. I've accidentally opened the dock by moving my cursor to the corner of the screen way too many times and it is sooo annoying. This never happens on GNOME because it's just not possible.
Also I tend to think itβs been designed for people who are more comfortable using a keyboard. Iβm mostly a mouse person.
That's absolutely true, but you can navigate GNOME completely with a mouse. If you're on a laptop, you can use the trackpad to flick between workspaces with three fingers. Every aspect of the GNOME desktop is navigable with the mouse, including the Activity Overview. GNOME's workflow changed the way I use computers.
One thing I miss from KDE is GNOME's tiling. KDE's is far more inconsistent. But there are a lot of things I like more about KDE too. I use it in basically the same way as GNOME.
I wonder if the same is going to be true of Thunderbird. Thunderbird actually requires you use Mercurial to contribute at all, rather than managing both git and Mercurial.
That being said...it's kind of odd to me how swiftly Mozilla of all companies/orgs is to embrace a code forge hosted by Microsoft for their main software. Surreal, even.
What really needs to happen:
Flatpak packages should ask for every permission they need, and the user needs to approve every one of them.
Right now, we have this weird in-between state where some flatpak packages ship with limited permissions (like Bottles). That's because every permission the package asks for is immediately granted. The user doesn't get a chance to refuse these requests. This current model serves to make life more difficult for non-malicious flatpak packagers while failing to protect users from malicious packages.
Also, GNOME needs a Flatpak permissions center like KDE. You shouldn't need to install a third party program to manage permissions.
It's worth mentioning that Android Auto doesn't work on GrapheneOS due to the privileged access it requires, and will not support it unless it is re-architected. Which phones were you thinking of when you said "compatible"?
Every Dell laptop I've ever owned has had a key repeat issue. Mind you, this was an issue on Windows too. Otherwise, I bought a Dell Latitude last year and it has worked great.
Installed KDE and GNOME at the same time. Ubuntu did not like that.