Live data from Hacker News

The Future of the Gitlab Web IDE

about.gitlab.com

91–100 of 168 posts

Re: The Future of the Gitlab Web IDE

#91

Running VSCode remotely introduces many interesting challenges, mostly due to security. (You are letting your users run any arbitrary code on your infrastructure.) However, I guess GitLab already has this sorted out, because of their existing IDE, and they are experts in this area. Also the open source versions of VSCode don't have access to the official VSCode marketplace. (Both VSCodium and coder.com Code Server.)…

It's all dockerized and security hardened probably. I'm guessing this is not that much of an issue. At least not any more than the likes of AWS, Google cloud, etc. allowing third parties to run whatever on their infrastructure. Not to say that there aren't any challenges but they aren't new challenges. And of course Gitlab has long been running CI infrastructure which would have the exact same issues.

Re: The Future of the Gitlab Web IDE

#92

It's interesting to me that GitLab is adopting a Microsoft product (VS Code) and Microsoft owns a significant competitor in GitHub. Nothing intelligent to say about that other than to wish I'd been a fly on the wall for the discussions about that. > Next, we asked ourselves the question: Do we want to continue to invest in implementing custom features for the Web IDE that ultimately deliver the same value as those al…

Microsoft may have a dominant position in developer tooling, but they don’t have a monopoly. A well-funded team could create a compelling competitor to VS Code. The issue is that there’s no money to be made duplicating the effort that has gone into VS Code when VS Code is open source. Even Google doesn’t seem to care about entering that space.

Google is weird, they want to conquer Cloud market but they dont do anything like VSCode or Github in dev community.

In 10 years Google regret not buying Github.

Re: The Future of the Gitlab Web IDE

#93
post #75

Earlier quoted context omitted.

> Yes. Because local development environments...break ALL THE TIME. This seems like more of a process problem than a technology problem. Our company has a simple rule for this: you break it, you fix it -- immediately. As a result, our development process is very stable.

How many hours a week on average do your engineers spend fixing something in their own environment that they broke?

Sounds like well spent hours. Why would you even consider working with engineers that cannot even fix the simple tools they break?

Re: The Future of the Gitlab Web IDE

#94
post #12

Maybe I'm getting old, but I don't want to do all development-related tasks in my web browser. As a software engineer, I want local control, where an internet connection is optional. I want to be able to experiment with the software in various local setups. I just don't get why Gitlab thinks this is a good idea worth a huge amount of engineering effort. Are people really clamoring for this feature?

Well, you don't have to of course but that does not mean others are like you. Also, it's not necessarily all browser based. The same thing running as an electron app is probably not that big of a deal.

I've not yet used a lot of remote tooling. But I routinely ssh into remote servers and I can see the appeal of not having my laptop running scorching hot all the time (I use Intellij a lot). Also financially it's not a bad deal. Pay a few tens of dollars per month and use a relatively simple laptop to access the remote setup. I wouldn't mind paying a little extra for some extra fast CPU if I can do it by hour.

Of course what Gitlab does is not that interesting. But e.g. Jetbrains closing a deal with Gitpod (which already runs their IDEs in the cloud) is a potentially a big deal. I could see myself giving that a spin at some point.

Re: The Future of the Gitlab Web IDE

#95

It's interesting to me that GitLab is adopting a Microsoft product (VS Code) and Microsoft owns a significant competitor in GitHub. Nothing intelligent to say about that other than to wish I'd been a fly on the wall for the discussions about that. > Next, we asked ourselves the question: Do we want to continue to invest in implementing custom features for the Web IDE that ultimately deliver the same value as those al…

maybe we'll live to see gitlab embrace, extend and extinguish vscode

Re: The Future of the Gitlab Web IDE

#96
post #89

Earlier quoted context omitted.

What IDE do you 'own'?

I guess that OP is talking about having the IDE/compiler/etc binary on their computer and not having to rely on any external service to work.

Well then self-hosted Gitlab is the perfect option.

Re: The Future of the Gitlab Web IDE

#97

By the way, Monaco is 10MB+. That's quite impressive nowadays for something so feature filled, but you're staying for 10MB when doing quick edits. Monaco is a mature, powerful and pluggable, which makes it a good platform to build on top of. More cynically, it's a good bang-for-the-buck project if you are seeking a promotion. The alternative is building your own. Maybe that doesn't make good business sense. And that'…

> under 14KB ( a single TCP roundtrip )

That's not a single roundtrip in any TCP stream I've heard of... Still, a lot smaller than 10MB of course.

Re: The Future of the Gitlab Web IDE

#98
post #92

Earlier quoted context omitted.

Microsoft may have a dominant position in developer tooling, but they don’t have a monopoly. A well-funded team could create a compelling competitor to VS Code. The issue is that there’s no money to be made duplicating the effort that has gone into VS Code when VS Code is open source. Even Google doesn’t seem to care about entering that space.

Google is weird, they want to conquer Cloud market but they dont do anything like VSCode or Github in dev community. In 10 years Google regret not buying Github.

Google had a viable GitHub competitor at one point. But they let it languish and then shut it down. It's a familiar story.

Re: The Future of the Gitlab Web IDE

#99

I want to own the code, own the software, own the tools (IDE, compiler etc) and also be the only one who controls them. And I want to also develop fast, not wait for some goddamn web app. And no, I don't need to code on my phone or tablet while travelling to Bahamas.

What IDE do you 'own'?

QtCreator? Vim? Eclipse? KDevelop?

And I'm just talking about C++ IDEs here.

Re: The Future of the Gitlab Web IDE

#100

I want to own the code, own the software, own the tools (IDE, compiler etc) and also be the only one who controls them. And I want to also develop fast, not wait for some goddamn web app. And no, I don't need to code on my phone or tablet while travelling to Bahamas.

What IDE do you 'own'?

Yeah, practically, it's the same. They don't even own git tbh, and won't even make noise on git core mailing list. I can even go extreme, practically, whether they even can.
Post reply on HN