Live data from Hacker News

Web IDE Beta

docs.gitlab.com

141–150 of 258 posts

Re: Web IDE Beta

#141

Anyone think there'll be another editor that'll surpass VSCode, similar to how VSCode surpassed Atom (and others)? I used to think that there would be one, but now I'm not so sure.

With language servers, I think the big IDEs will be less relevant. It'll be easier for anyone to write a text editor with language server integration and make it with just the way they like.

You're forgetting the actual heavy lifting that proper IDEs do, and that VS Code leaves to language implementors. Unless you know how to do proper code analysis, you won't be able to make it "just the way you like".

Even writing a proper IDE-aware compiler is a quite a daunting task.

Re: Web IDE Beta

#142

I've been using a web IDE in Gitlab for months... what changed?

GitLab team member here.

We released a beta version of our new Web IDE which is built using VS Code. The new Web IDE will provide users access to more features, improved performance, and the ability to securely connect to a remote development environment directly from the Web IDE.

Re: Web IDE Beta

#143

Earlier quoted context omitted.

Unlike IE, VS Code is open source though. If Microsoft does some terrible thing with VS Code, the community can just switch to VSCodium: https://vscodium.com/

Can? The time to support FOSS is now.

Which Visual Studio Code is.

Re: Web IDE Beta

#144

I tried the JetBrains remote IDE, it was awful. Sad since I'm sure it was amazingly hard to get to that point and they poured a lot into it. There's just so many resources and so much process tied to the local environment outside the IDE, this was light years away from making sense. I'm keeping an open mind, though, maybe some day.

Try VSCode Remote, works wonders and simply.

Re: Web IDE Beta

#145

I don't understand that girls is letting that going when they pretend to care for OSS. Microsoft is in the embrace phase, there is not a major forge that will remain that will not force to use their things. Then they will be able to start with messing things, like requiring proprietary extensions to lock down the thing. I guess a lot of people here don't remember the good old time of Visual Studio on Windows.

This seems alarmist for no founded reasons.

> Then they will be able to start with messing things, like requiring proprietary extensions to lock down the thing

Some extensions are already closed source: Remote Development, Python, and probably tons of other which I didn't even notice. So what? What does it change in practice? What's stopping anyone from creating their open source alternative if it bothers them?

Now let's say they "extinguish" their extension ecosystem. Then they die and everyone switches to VSCodium and open-vsx for extensions. Again, what's the problem?

I honestly think they're in a position where not only the EEE is not their strategy anymore, but also it's not even doable with the state of VSCode.

Now, what exactly are your arguments?

Re: Web IDE Beta

#146

Earlier quoted context omitted.

Well, they can just fork if something happens, no? Or even phase out this product, if something goes that wrong.

Many core features like remote editing and python support use a DRM so they only run in VSCode and not forks.

These are NOT core features. They're literally extensions. Anyone could create an alternative for both of these if they wanted it.

Re: Web IDE Beta

#147

I've been using a web IDE in Gitlab for months... what changed?

GitLab team member here. We released a beta version of our new Web IDE which is built using VS Code. The new Web IDE will provide users access to more features, improved performance, and the ability to securely connect to a remote development environment directly from the Web IDE.

With all due respect (big GitLab fan here) there are at least two features that are missing that for me makes this product unusable:

1. Inability to switch branches in the editor [0]

2. Full project search "to be enabled at a later date"

So I can't switch branches off of the default branch and I can't search the entire project. To me, this undermines your claim that the new web IDE "will provide users access to more features" and in fact I don't find it useful for hardly anything in its current state.

I get that it's a beta, but it seems a very incomplete one, at best.

[0]: https://gitlab.com/gitlab-org/gitlab-web-ide/-/issues/72

Re: Web IDE Beta

#148
post #143

Earlier quoted context omitted.

Can? The time to support FOSS is now.

Which Visual Studio Code is.

It's not. VSC is a packaged version of the open-source code with proprietary bits added. Integration with the plugin marketplace, telemetry, etc. VSCodium does not have that.

In addition, a lot of the good language plugins are proprietary, like PyLance and the C# plugin.

Re: Web IDE Beta

#149

I don't understand that girls is letting that going when they pretend to care for OSS. Microsoft is in the embrace phase, there is not a major forge that will remain that will not force to use their things. Then they will be able to start with messing things, like requiring proprietary extensions to lock down the thing. I guess a lot of people here don't remember the good old time of Visual Studio on Windows.

VScode’s killer feature is its remote development capability.

Its prevalence could had been averted if Linux folks were not that stuck in command prompt editors for ssh work, and lecturing beginners about their incompetence to learn the keyboard commands of vi.

At some point there was some work in forwarding UI via X11, but it was very clunky and slow. The Remote Desktop capabilities of Linux are also atrocious for rendering text.

So here we are, Microsoft covered the gaps that the community underplayed for decades, and now is dominating.

Re: Web IDE Beta

#150

I tried the JetBrains remote IDE, it was awful. Sad since I'm sure it was amazingly hard to get to that point and they poured a lot into it. There's just so many resources and so much process tied to the local environment outside the IDE, this was light years away from making sense. I'm keeping an open mind, though, maybe some day.

Try VSCode Remote, works wonders and simply.

This is one area I'll never jump ship. I like developing the code I write on a local machine. If some day in the distant future we are required to use cloud servers to develop, I'm out. Done. Adios.
Post reply on HN