Re:Gitlab.com Is Moving to 13.0
by efiecho on Sunday May 10, 2020 @04:45PM
(#23136011)
I find it very frustrating that Gitlab requires Javascript for simple basic things. You can't view replies to issues or even browse files in a repository. GitHub UX is so much better, but sadly many projects moved to Gitlab because of Microsoft acquiring GitHub.
[ Parent
| on HN ]
> I find it very frustrating that Gitlab requires Javascript for simple basic things. You can't view replies to issues or even browse files in a repository. GitHub UX is so much better, but sadly many projects moved to Gitlab because of Microsoft acquiring GitHub.
How much coverage does the API have? In theory it should be 100% as the website uses (as far as I remember, haven't looked into the source) Vue.js but I'm not sure in practice. If the coverage is 100% or near 100%, you should be able to do many of the things in the terminal or it is possible to have a completely server-side web application (not sure of the exact terminology, I mean like the delightful SourceHut[0] thing). The biggest concern is ongoing maintenance as Gitlab tends to move pretty quickly.
Personally, I'm hoping more of those folks move over to SourceHut[1]. It doesn't require JavaScript for anything, and it's much faster to boot.
Which projects that you follow moved from GitHub to Gitlab? None of the ones I keep an eye on have moved.
I don't really see the point. GitHub has only improved since they were acquired.
> I don't really see the point. GitHub has only improved since they were acquired.
Fully agree, but apparently some projects don't like having their infrastructure owned by Micosoft, that would be the only reason for switching in this case.