Hacker News Reader

Comment by tommoor | Hacker News Reader

I'm sure he'll have his usual blogpost moaning about how Gitlab already has it by end of day.

Why wait until the end of the day on the west coast? :) We just posted https://about.gitlab.com/blog/2020/05/06/git-challenge/ where we encourage you to compare:

1. GitHub Insights with GitLab Insights, Contribution Analytics, Issues Analytics, Productivity Analytics, Value Stream Analytics, DevOps Score, Code Review Analytics, and CI/CD Analytics.

2. GitHub security features with GitLab Container Scanning, Dependency List, Dependency Scanning, Dynamic Application Security Testing (DAST), Security Dashboard, Static Application Security Testing (SAST), and Secrets Detection.

3. GitHub Codespaces with the GitLab Web IDE, CI/CD Environments, Review apps, and Live Preview.

I'd definitely encourage everyone to git GL a try - our teams switched over from GH + Jira about a year ago, and haven't looked back. The integrated CI and project management features are a game changer.

I have to agree. I have been a big champion of GH but the more I use GL the more I keep asking myself why I don't just do all my stuff in GL.

Git it a try, pun intended? :-D

'Twas a simple typo, but I'll happily retcon it into a pun!

GitLab is also faster at cloning than GitHub. Whenever I have to clone a bunch of website repos to update templates for my website generator the GitLab repos finish cloning first even though I start them last.

To be fair, nothing was announced today by GH that wasn't in GL for several years.

Perhaps the quality of VS Code trumps GL WebIDE ... But I am not the sort of developer to ditch my desktop editors / IDEs for something running in a browser (electron or otherwise).

I think the most important thing that most people maybe forgetting is, GitHub maybe announcing these features, but these features were the results of acquiring companies that were solely focused on these features for years.

So if you take this into consideration, GitHub's feature has not only been in works for a while, but they have been refined to a point that GitLab will have a hard time catching up to.

There is no way GitLab will be able to compete on the IDE front-end for a while since GitHub's solution is essentially VSCode which they own and is iterated on at an incredible rate. And the one thing Microsoft hasn't made open source, that makes remote work incredibility powerful, is what makes Codespace incredibility difficult for GitLab to compete with.

Their security scan feature is the result of acquiring a leader in the field with expertise that GitLab will have a hard time matching/hiring for. And GitHub's Insights feature is the result of multiple acquisitions with years of previous experience.

These announcements maybe new, but the solutions that GitHub has released are years ahead of GitLab's existing solution.

I think that you are wrong on VS Code Remote not being open source. Here is the relevant repository: https://github.com/microsoft/vscode-remote-release. Corresponding official documentation (https://code.visualstudio.com/docs/remote/remote-overview) states that Visual Studio Codespaces is essentially a managed service of Visual Studio Code Remote Development. BTW, there is also an interesting alternative, the `code-server` project (https://github.com/cdr/code-server).

P.S. FYI: The TLS certificate on https://gitsense.com has expired.

I vaguely remember a post a while back (maybe a year ago) where they said they can't make a part of their remote technology open-source. Maybe things have changed, but I was quite sure it was something they were keeping close to them.

Also thanks for pointing out the certificate issue. I was actually leaving it that way on purpose, but I guess it can reflect poorly on my product, so I should just update the landing page with something non-descriptive.

Perhaps, you're right (or maybe not :-). Frankly, all this stuff, while interesting and eventually useful, is a bit low on my current priority list ... Re: certificate - You're welcome.

That repo doesn’t have any code in it, it’s used purely for issue tracking and syncing with the VS extension repo, I believe.

My bad. Apparently, you're correct. It seems that relevant code is a part of VS Code codebase. Perhaps, this is it (though, I very well might be wrong on this, too): https://github.com/microsoft/vscode/tree/master/src/vs/workb....

Reply on news.ycombinator.com