• 1 Post
  • 59 Comments
Joined 1 year ago
cake
Cake day: June 12th, 2023

help-circle

  • They will try. This is about OS-level APIs. In order for a browser to to install and run PWAs, it needs certain OS APIs for e.g. home screen installation, storage and notifications. iOS currently has these APIs but Safari severely limits what you can do with it. Now the DMA will force Apple to accept other browsers, which have no such limitations. So, Apple now wants to remove these APIs altogether and kill PWA support outright, before that portion of the DMA takes effect.

    There probably will be a lawsuit and Apple will probably lose, but it will take years to resolve that. And in the mean time PWAs remain dead and the only way on the iOS home screen in paying the 30% app store cut.







  • Distro maintainers are a lot better about keeping libraries up-to-date than random application developers. They will even patch applications to work on newer libraries, even when the app developers do not.

    There’s also auditability. If e.g. OpenSSL (or some other library) gets a high rated CVE and Debian ships a same-day patch, I know I am safe. I can verify that I have installed the patched version, and I know my applications use that patched version. Not with flatpak. Now I’m at the mercy of a dozen app developers, many of which probably value security less than the Debian Security team.

    IMHO it’s a mistake for Fedora to drop its own packages for flatpak. But Fedora appears just to be a RedHat experiments playground these days, not a user focussed distro.

    Don’t get me wrong, Flatpak is fine if you want to install stuff from Joe Random Developer off the internet, but I trust the Debian maintainers a whole lot more. If they ship it, i can trust it.



  • Distro native packages are:

    • Better integrated into the base system
    • No maintenance for the devs (they are usually maintained by distro package maintainers)
    • Better interoperability with other packages and dependencies, thanks to the package maintainers
    • No duplicate or outdated dependencies
    • More space efficient because they use system dependencies instead of packaging their own
    • Launch even quicker since they don’t go through flatpak
    • No missing or broken features due to flatpack limitations or sandbox issues (e.g. inter-process communication)

    If an application is new or niche or small then flatpak is definitely a good option. But if there’s a distro native package then that one is almost always the better option. Flatpak is nice for when there is no native package.










  • I have far too many windows open to display everything at once, even with my 3 widescreen monitors (the curse of being a developer). I usually need about 4-5 workspaces to organise everything. Sometimes more. Often there are also multiple windows arranged on a single screen (I use tiling, so windows never overlap). I know by heart which application is on what workspace and screen (because it’s always the same). Because each workspace has a hotkey (Win + a numbered key) I can instantly pull up any window that I need, without searching for it.