Wasn’t vertical integration, was done by packager.

We don’t believe that the openSUSE Deepin packager acted with bad intent when he implemented the “license agreement” dialog to bypass our whitelisting restrictions. The dialog itself makes the security concerns we have transparent, so this does not happen in a sneaky way, at least not towards users. It was not discussed with us, however, and it violates openSUSE packaging policies.

Not by default, but you can optionally enable it.

Ah I had the same issue. JavaFX still uses X11. By default VSCode only lets X11 be used if Wayland is not available (this is the X11 fallback permission). Disabling X11 fallback will let VSCode use Wayland and let JavaFX use X11. I might make an issue for this on the flatpak’s GitHub asking for this change.

Honestly, the truth is that setting up containers for development will always be a hassle. My low tech way is just to make a distrobox container with its own home folder, install an IDE in it, and install packages. The more proper way to do it would create your own containerfile to build your container for developing.

VSCode also has its DevContainers extension but that doesn’t work in VSCodium and does some weird things.

Flatpak’s usefulness for programming depends on the IDE and language. IDEs like VSCode largely suck because they are not designed to work in flatpak. But some languages still do work well in them, such as Rust, since Flathub provides the Rust SDK and dependency management is done with cargo. But it sucks for C++, where you typically install dependencies using your system package manager.

IDEs like Gnome Builder are pretty good. It’s designed to work within the flatpak sandbox. Even when running as a flatpak, you can choose to build things using containers or your host system. And of course also build using the Freedesktop runtimes.

I recently setup JavaFX with the flatpak version of VSCodium and have it working pretty well. You first need to install the Java SDK from Flathub, set an env variable to tell VSCode to load the SDK. The more annoying part was JavaFX since it’s not part of the JDK anymore. I just downloaded the JavaFX tar, extracted to a directory called JavaFX, and set $JAVAFX_HOME to point to it. Since VSCode has host filesystem access, it can access it. Few more steps than traditional Linux, sure, but still easier than MacOS and Windows.

Not sure about your database situation though.

Major people of the project had moved on. It’s being maintained, getting security fixes, but pull requests are slow to be merged.

That is planned. But pulse is not secure, so exposing it is not great.

Don’t believe so, best that’s currently available is skimming through the video to look at the slides.

Here’s my short summary of the presentation, I tried to denote what’s being worked on (open PR), what’s kinda being done (WIP), and things stuff they’d like to be done in the future (wishlist). May be somewhat wrong.

• Flatpak is stagnant
• Red Hat is working on a better way to preinstall flatpak apps (open PR)
• Flatpak should is slowly moving towards OCI and away from ostree (more tooling available, don’t need to maintain their own tools)
• Better permission handling that is more backwards compatible (open PR)
• Should directly use Pipewire instead of Pulseaudio (WIP)
• Allow user namespaces in flatpak sandbox (WIP)
• Move dbus proxying into dbus brokers (wishlist)
• Improve network sandboxing (wishlist)
• Improve drivers handling, currently drivers need to be built for each runtime, could cause issues if using EOL app on new hardware (wishlist)
• Work on portals directly improves flatpak

Unfortunately, it’s not in a great situation. Flatpak is stagnant. There’s a lot of cool things in the works, like a stronger sandbox, preinstalling flatpaks more effectively, etc, but merging things is hard.

That laptop setup is actually insane. I love the “roleplay” he had set up for it, making it seem like a computer used at a nuclear reactor (though the more realistic setup would have been to install Windows XP with default background).

Also funny to see him doing more complex things like setting up a systemd service to hide and show waybar dynamically.

FOSS also depends on them, many FOSS contributors are employed by proprietary companies.

Papers forked from Evince.

I love when I try to open a file and macOS tells me I can’t because can’t tell if it’s safe. There’s literally no way to open it from here.

You have to hit ok, then go so settings, scroll down to security, and hit a button to specify yes I actually want to open this file. It then reprompts you again but now with an open anyway button.

I love my MacBook’s hardware and battery life, but MacOS is such a letdown.

I don’t think that’s the case here. This is Lutris, a GTK3 app. There shouldn’t be any GTK changes breaking themes here. It seems like OP’s theme is just broken.

This is overly complicated. Just install Java then run

flatpak --user override --env="FLATPAK_ENABLE_SDK_EXT=openjdk" com.vscodium.codium

Note this works for all other SDKs too. It works especially well for programming languages like Rust that have their own package manager.

Doesn’t work so well for languages like C/C++ where you use your distro package manager to install dependencies. In those cases it’s easier to install VSCodium inside a container where you do have access to a distro package manager.

The kernel is a snap in Ubuntu Core, but you still need to reboot. I don’t think there’s a nice way to work around that.

Fedora IoT is similar to CoreOS, that seems primarily aimed towards Pis.

I haven’t watched the video yet, but keep in mind “resource usage” being lower isn’t always better.

For example, Plasma had an issue for some people where animations would not happen, freeze the system momentarily, and stutter. The reason why turned out that these people were using slow drives. Plasma was trying to load the bytecode for the QML animations from disk, but the IO operation took too long so the animation suffered. Had this bytecode been stored in memory, the performance would have been better.

But I also don’t want to discount the fact that some (perhaps most) of the time, high resource usage is a bad thing caused by poor programming and using technologies that are heavier, like Electron. Whether those tradeoffs are worth it are another matter.

I wish more developers actually used their software low-end devices to find performance issues. I recently got an Intel N100 and it’s actually been a decent experience on Linux, though Gnome shell’s animations are a bit stuttery even on Gnome 48. Haven’t tested any other desktop though.

@Zamundaaa@discuss.tchncs.de

It’s not making it worse. They like anime, so they have an anime girl as the mascot; a very tame one too.

But some people freak out about it.

If you use Anubis for free, he asks that you keep the girl on for marketing purposes.

If you pay / support the project, you can remove it.

Honestly, it’s a good way to encourage people to pay up because some people absolutely hate it.