amazari

It is LibreOffice at its heart, but wrapped with a web-techs UI, AFAIK.

You know that all the Wayland primitives, event handling and drawing in gnome-shell are handled in C/native code through Mutter, right ? The JavaScript in gnome-shell is the cherry on top for scripting, similar to C#/Lua (or any GCed language) in game engines, elisp in Emacs, event JS in QtQuick/QML.

It is not the performance bottleneck people seem to believe.

Came here to note that contrary to what is said here, Lollypop is not "new", nor is it representative of current so-called "GNOME-isms".

It uses UI idioms and technologies (gtk 3) of its mileage, 2017.

Indeed, their work on WebKit, Servo, Mesa drivers, the kernel, and more is seriously impressive!

Their customers, Valve, in this case, deserve credit for being good FLOSS citizens (even if they are building a DRM walled garden on top of it :/), but the actual workers are the real unsung heroes. Them, Codethink, Collabora, and other open-source consultancies I might have missed are doing the community a huge service."

So this is AMD catching up with Nvidia in the RT and AI upscaling/frame gen fields. Nothing wrong with it, and I am quite happy as an AMD GPU owner and Linux user.

But the way it is framed as a revolutionary step and as a Sony collab is a tad misleading. AMD is competent enough to do it by itself, and this will definitely show up in PC and the competing Xbox.

Well, at least xdg-app has the concept of "runtimes" shared among applications. If a lib/bin in a runtime has a security issued, the whole runtime might be updated. Transparently for the apps running over it. A runtime might be FreeDesktop-1, Gnome-3.14 for example. Lets say a 0day is discovered and patched in gtk 3.14, a new version of the Gnome-3.14 is issued and dl by the clients. Magically (with the help of overlayfs and co) all the apps depending on this specific runtime have a secure gtk.

> No, it's not. The serverside is implemented in Scala using a JGit as a GIT library for the files and H2 database for saving the metadata.

From a quick scan of the sources, H2 seems to be an hard-coded dependency. Do you have any plan on abstracting the Slick driver to allow others DB providers ?

I guess the major advantage of this solution over github is its source availability under a FOSS license (Apache).

The story's title might indeed be more informative by stating that instead of focusing on the implementation language.