Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The Future of the Gitlab Web IDE

about.gitlab.com

Post reply on HN
Print view View original

161–168 of 168 posts

Re: The Future of the Gitlab Web IDE

#161

Post by greatgib »

greatgib wrote: post #138
greatgib wrote: post #101

Always have to check the date for April's fool day when seeing a news like that, but sadly it is not... When you think that gitlab started as an open source alternative to the closed world of GitHub, and was free as in "free speech". And then, little by little it becomes the same thing. Less and less things not in premium plan and less affordable plans. Now, they are ok to use as-is a Microsoft editor, that is free a…

Vscode is not free btw: https://news.ycombinator.com/item?id=31488436 The thing is always the same, in OSS you get for free a little bit less good version of VSCode. But you get used to it, competitor development is killed little by little, like in the current case. And, when everyone is "hooked", and every one and companies are used to it, you can slowly reduce/limit the oss version and push everyone to the the prop…

Thanks for the notice for the link. Sadly I can't edit anymore... Here is the good one: https://carlchenet.com/you-think-the-visual-studio-code-bina...

Re: The Future of the Gitlab Web IDE

#162

Post by happymellon »

rizzaxc wrote: post #153
happymellon wrote: post #79

Earlier quoted context omitted.

His comment was more that the juniors that he mentors break their environments. The junior breaking their environment is usually self inflicted. Besides to fix this, you still don't need to run everything remotely. [Edit] In my experience, the biggest slowdown to being productive is corporate lockdown of laptops, but then no support from corporate for getting a development environment set up. So the first 2 weeks on…

more like because the language is a non obvious clusterfuck that requires self-inflicted pain to be productive in. sounds like a good use case for a remote container not to mention, pair programming/ merge review will be easier, making guiding juniors more efficient. of course i'm not saying it'll be all positive but there are legitimate reasons gitlab is doing this

If we were allowed to use a real OS, you could just run local containers. Or hell, this was solved with Vagrant how many years ago?

Why does it have to be remote?

The whole point is that I don't always have internet access, sometimes there are outages and sometimes it's just plain slow for some reason. It's shit enough all the video calls I have to be involved in these days, not as bad as all the face the face meetings in crampt rooms with everyone falling asleep because of the lack of air circulation. Why do you want to make the development environment crappier?

It also isn't clear how it would make code reviews better, or even paired programming? Shared workspaces are already a thing.

Re: The Future of the Gitlab Web IDE

#163

Post by smileybarry »

infogulch wrote: post #159
tex0 wrote: post #143

Earlier quoted context omitted.

Oh. I thought you were talking about a viable GitHub competitor ;)

What made it unviable except letting it languish and then shutting it down?

It had what was essentially an HTML4 UI and just SVN support for what seems like forever. I can't remember a version of it that didn't look like 2005 Gmail.

Re: The Future of the Gitlab Web IDE

#164

Post by webmaven »

smileybarry wrote: post #163
infogulch wrote: post #159

Earlier quoted context omitted.

What made it unviable except letting it languish and then shutting it down?

It had what was essentially an HTML4 UI and just SVN support for what seems like forever. I can't remember a version of it that didn't look like 2005 Gmail.

Hence "languish". When it was first made available in 2006, it wasn't an also-ran.

Re: The Future of the Gitlab Web IDE

#165

Post by webmaven »

JeremyNT wrote: post #146
zarzavat wrote: post #69

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.

> 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. I would argue that the best thing to come out of VS Code isn't even "VS Code" the overall environment, it's LSP [0], and MS has given that back to the community such that anybody can use it in a competing editor. I don't really think "VS Code" the product h…

> I don't really think "VS Code" the product has a "moat" here and (up to now, at least) MS hasn't demonstrated much intent on creating one.

As far as I can tell, Microsoft's moats here are things like Teams, Live Share, and Remote. If anyone has or is working on open source implementations that can be installed into the open source version, I'm sure there would be widespread interest.

Re: The Future of the Gitlab Web IDE

#166

Post by webmaven »

echelon wrote: post #45
daenz wrote: post #15

Earlier quoted context omitted.

The ailments you describe can be resolved by having a small dedicated Developer Experience team. Their mission is to ensure that developers can ramp up quickly with deterministic environments and keep a high velocity with developer tooling. If a big company doesn't have one, they're messing up. I see the benefits of having something that "always works" though the browser, but for me, the lack of control does not outw…

> The ailments you describe can be resolved by having a small dedicated Developer Experience team. This is a cost center and will be underfunded in most companies and orgs. Companies want to focus on their core competency. Also, devenv is non-standard across companies. If a company wants a truly interchangeable workforce, they want standard tools that look the same everywhere. > but for me, the lack of control does n…

> The future is thin clients. It's not just going to be our industry, either. Every creative industry is going to undergo this change.

It is worth noting though that the thin clients are mostly going to be equivalent to a Chromebook, which is considerably beefier than top-of-the-line developer workstations from only a few years ago.

Re: The Future of the Gitlab Web IDE

#168

Post by rmetzler »

eschurter wrote: post #150
rmetzler wrote: post #44

Earlier quoted context omitted.

There is also https://www.gitpod.io/ I like the current WebIDE. It has two features which are important to me: - Lauch it with the . hotkey, from the file or merge request you currently browse - multi cursor with CMD+D on a Mac I don’t think I need VSCode, but we’ll see.

GitLab team member and OP author here. I'm glad you enjoy that `.` hotkey! Don't worry, it won't go away! I'm about 90% sure multi cursor works the same way, but I'll verify and make sure we don't take a step back there :) I hope you find value in the other features we'll be delivering as part of the VS Code transition!

I mentioned the CTRL+D multi cursor specifically because I think this feature is only available in VSCode if you choose the Atom key bindings. I regularly try to show this to my colleagues whenever we’re pairing, but they need to fall back to search & replace in VRSCode.
Post reply on HN