Naturally these kinds of having a language island create some attrition regarding build tooling, integration with existing ecosystem and who is able to contribute to what.
So lets see how it evolves, even with my C bashing, I was a much happier XFCE user than with GNOME and GJS all over the place.
It is not the performance bottleneck people seem to believe.
It uses UI idioms and technologies (gtk 3) of its mileage, 2017.
Everytime their name pops up it's inevitably "oh some thankless extremely technical low level work leading to impressive/long-awaited features"
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."
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.
I think its a step backwards, as you loose tight control over dependencies. E.g., in case of a security issue, one cannot easily patch all containers if they are blackboxes.
IMHO, the right tool for this is an improved package manager such as Nix or Guix (which incidentally also support containers in their own way). Perhaps the future should be a Nix-like package manager for dependency management, and container-ization for security and resource limits.
This is not a "full clone" but "something like GitHub" but for your own private server.
> I understand that the server-side implementation is based on GitHub as a black box
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 ?
It's quite possible that gitbucket is better than github or gitlab for some reason, and if so I'd like to know that reason; "It's identical on the surface and different under the hood (not necessarily better, just different)" doesn't seem like a particularly great way to generate interest...
The story's title might indeed be more informative by stating that instead of focusing on the implementation language.