Sure, but some countries are more neutral, hosting in Switzerland would be for sure better, while USA is probably the worst choice.
And you wouldn’t need to worry about it if you could host your own server and be able to communicate with other servers, like Lemmy is doing, you get the best of both worlds
They had to do it, but this is the downside using a git server hosted in non neutral country. You never know when USA will decide to impose sanctions on a country for whatever reason.
It is one of the reasons many European companies do not use Github, as it is USA based.
Well not really, you would need an account in the organization in order to create issues, pull requests for a privately hosted instance. You can see the public repository but apart from cloning you cannot do anything else.
While Gitlab.com is centrally hosted, not much different than Github, you still cannot communicate with other Gitlab hosted servers.
Thanks. There is also a Gitlab issue requesting this feature, which I am tracking.
It needs to reach a polished state before organizations and university adapt it. So something like what you linked probably wont fly.
Advantage of Github over Gitlab is code discoverability. My organization hosts Gitlab instance but I would still rather host my open source project on Github instead, because its impossible to collaborate on Gitlab with external users who dont have an account on our instance.
Once there is a federation feature similar to Lemmy, I would be happy to host everything there.
I was using I3 and now sway. But I never felt any real difference in performance. Other than better 4K and multimonitor support, why i switched. I was wondering if Hyprland is just for looks or it brings something important
What WM did you use on EOS, and what is the improvement in Hyprland?
But how can I see kbin content from lemmy, I couldnt find an option yet. Also from kbin I cannot find lemmy communities
Because it’s an open Instruction Set Architecture.
Many different companies used to design their own CPU IS architectures in the past like (MIPS, AVR, PIC, …) and of course the most popular ARM. Downside of this is that the software and ecosystems between these architectures are not compatible. Effort wasted in porting a library to one architecture cannot be always reused for another.
Recently we see a lot of companies adopting RiscV, and there is a big collaboration between them to ratify the specification and provide software support. This will in turn accelerate the development, and software and hardware support will hopefully overtake ARM in the future.