Live data from Hacker News

GitLab Web IDE

about.gitlab.com

211–220 of 280 posts

Re: GitLab Web IDE

#211
post #68

Earlier quoted context omitted.

What we need is a web deliverable (i.e. not a "web technology based" Electron desktop app) Neovim frontend. Something like a Wasm & WebGL based UI layer connected via msgpack to the editor core that's running in a sandbox on GitLab's infrastructure. I'm truly sorry if the above drivel is either impossible or insane; as an embedded guy this is most definitely way outside my wheelhouse. I should get back to repairing m…

Why do we "need" this? It sounds overly complex and error-prone.

Just read the last part of their post, and you will understand.

Re: GitLab Web IDE

#212

Earlier quoted context omitted.

You speak about Cloud9 as if it's not available anymore, and that may not have been your intention, but I'd like to make it clear: Cloud9 still exists, and you can still use it. It's just accessed through the AWS portal. If anything, it's even more of a value proposition today due to EC2 auto-shutdown saving money when you're not using it, and even more useful since it's running on your own VPS you can do whatever yo…

I think it's a justifiable reaction, similar to the one after Microsoft's acquisition of GitHub. When an 800 pounds gorilla pays a bunch of cash to acquire a successful independent product, they do so either to quench a potential rival or to embrace and extend into that field and leverage their traditional offering. It makes sense from a business perspective, and they are the only ones capable of paying that much cas…

Genuinly curious: is there a (relatively cheap) cloud vendor that doesn't do that? MS & G seem pretty similar to me...

Re: GitLab Web IDE

#214
post #207

Earlier quoted context omitted.

Unix philosophy does not work on the web because even with all the talk about micro services, you can not easily chain or combine web tools together.

But why write code on the web? If you are typing you are already on a computer

Conversely, if all you need is a web IDE that abstracts individual tools away, why bother dealing with them? Setting up and maintaining a development environment environment is at best annoying and at worst daunting, especially if you're a beginner.

Re: GitLab Web IDE

#215
post #45
post #39

> We are planning for an even better experience in the future: one where we can integrate and support more advanced features, such as a live environment to test your code against This. Please. I'm playing with a similar concept for GitHub: https://twitter.com/pomber/status/1003416752146075648

One day, I can toss out all my expensive hardware and do my job with a hi-res Chromebook and steady wifi.

One day you might not have a choice because the desktop is so locked down.

Re: GitLab Web IDE

#216
post #207

Why are people building these verticals? What happened to Unix philosophy? Build tools that do simple things, and make composition do the work for you. I don't see why anyone needs an online IDE. Much less one interfaced with Gitlab. What next, invent a new cpu too?

Unix philosophy does not work on the web because even with all the talk about micro services, you can not easily chain or combine web tools together.

What does that have to do with editing text?

Re: GitLab Web IDE

#217
post #44
post #17

What is the use for this? I mean how many people actually use such tools for actual day to day dev? Maybe for some quick edit if you don`t have laptop/computer at hand, but otherwise I see no real advantage of this.

I've actually been using it for the past month or two and it's been pretty solid. My particular use case is that I'm using GitLab pages and can use the Web IDE as a poor man's CMS tool. Edit/preview the markdown and upload images, then commit and have the CI pipeline pick it up and deploy. I can see myself editing config files, READMEs or possibly markup. Real coding would likely end up frustrating as hell. Ironicall…

Can you test everything before you commit? Like you would do if you did it locally.

Re: GitLab Web IDE

#218

Why are people building these verticals? What happened to Unix philosophy? Build tools that do simple things, and make composition do the work for you. I don't see why anyone needs an online IDE. Much less one interfaced with Gitlab. What next, invent a new cpu too?

Just because it's unified at the presentation layer doesn't mean its design doesn't follow the Unix philosophy. The problem is that even if the web was composable (`gitlab.com | jenkins.com | tee cloud.google.com aws.amazon.com`), it probably wouldn't be accessible to most users.

Unix philosophy is great for system builders, but system users want the car, not the tools and parts.

Re: GitLab Web IDE

#219
post #207

Earlier quoted context omitted.

Unix philosophy does not work on the web because even with all the talk about micro services, you can not easily chain or combine web tools together.

But why write code on the web? If you are typing you are already on a computer

Lots of companies do their development work on per-developer remote VMs, especially for resource-intensive applications that need nontrivial configuration-management setup for databases, message queues, etc. that they depend on.

Currently your choices are emacs/vim over SSH or sync from your local machine (where the code intelligence / debugging integration probably doesn't work as desired).

A web IDE allows an arbitrarily powerful cloud instance to do the heavy lifting of build/test/code intelligence while the developer still gets a full-featured GUI IDE. Especially since VS Code and Atom are Electron apps, it's a natural step to use them to edit remote files. Better than VNC, anyway.

Re: GitLab Web IDE

#220
post #17

What is the use for this? I mean how many people actually use such tools for actual day to day dev? Maybe for some quick edit if you don`t have laptop/computer at hand, but otherwise I see no real advantage of this.

Hey there. I'm the developer who made the POC. My original idea came after watching non-technical people try to make changes to the readme. They would have to ask for a lot of help to get the terminal open or use a GUI. When really all they wanted to do was make a quick change. The idea is that there's a lot of different users using git and I want to make it accessible for everyone.

Why do you want non-technical people to be able to edit the readme? That's for programmers to communicate to programmers. A little knowledge is dangerous. Keep non-technicals away from git.
Post reply on HN