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

Web IDE Beta

docs.gitlab.com

Post reply on HN
Print view View original

171–180 of 258 posts

Re: Web IDE Beta

#171

Post by john_cogs »

alias_neo wrote: post #158

> with an implementation inspired by Visual Studio Code. Is this an indication of Gitlabs new "corporate" culture? The website already seems less "OSS" than it did, but to say "inspired by" is a hairline away from bullshit. It's not inspired by VSCode, it _is_ VSCode.

GitLab team member here.

Thanks for the feedback.

I created a merge request to update our documentation based on your comment and linked to the comment in the MR description: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/107599

Re: Web IDE Beta

#172

Post by yjftsjthsd-h »

john_cogs wrote: post #142
WFHRenaissance wrote: post #132

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.

> improved performance

Huh, that's surprising but probably good. My initial reaction on reading that you were replacing your own thing with VSC was something like "aw, now it'll be too slow to use". Hope you're right:)

Re: Web IDE Beta

#173

Post by yjftsjthsd-h »

azalemeth wrote: post #88
morelisp wrote: post #43

Earlier quoted context omitted.

I see your profile says you’re in your early 20s, so I kind of understand the question but also I’ll be blunt: yes, there will be another text editor. 90% of the tools you use today will be gone by the end of your career.

And the remainder will be called things like vim, emacs, awk, and sed ;-)

I forgot the name of the principal, but there's a rule of thumb that a thing's future life expectancy is related to how long they've already been around. So in general if some new text editor emerges, I give it a reasonable chance of being dead in 6 months. VSC is old enough to probably be around for a while now. And I fully expect emacs and vi/m to outlive me:)

Re: Web IDE Beta

#174

Post by iudqnolq »

notpushkin wrote: post #100
vladvasiliu wrote: post #63

Earlier quoted context omitted.

You already have that with Idea, with a few exceptions (C/C++, and possibly C#). You can install the Python plugin & friends -> PyCharm You can install the Go plugin -> Goland Etc

I'm not sure why, but nobody I know uses this setup – everybody has 2–3 separate IDEs (one for backend, one for frontend etc). The initial reason behind having separate IDEs for every language, or so I was told, was using different keybindings. This way, XCode users could easily switch to AppCode, Visual Studio users – to Rider etc. – without the need to re-learn anything. (This is the reason I still have Atom keybin…

Like my sibling described there are weird quirks. The bigger problem is that this isn't a well documented and supported path. And if you wanted to spend time fiddling with my IDE you wouldn't be using Jetbrains.

Re: Web IDE Beta

#175

Post by theptip »

btown wrote: post #136
morelisp wrote: post #28

Earlier quoted context omitted.

JetBrains seems to be forging ahead with their own Space project and not trying to partner too closely with any existing forge. They seem to understand "IDE-in-browser" undermines their fundamental market position; they need to make people not need the browser in the first place, to retain it.

JetBrains' fundamental market position is that companies pay per seat for an it-just-works IDE. So if anything, IDE-in-browser, where code is executing on a hosted backend, is even more aligned with this. The real question is whether they can execute on this. Will they be able to replicate years of VS Code's work on providing UI extensibility without sacrificing performance, with a team that historically had been JVM…

I’m confused by this comment. Why do they need to move to browser-based JS/TS?

Their existing toolchain is all about doing everything in the IDE. (Remote dev envs, code review, all of it).

Am I missing something? I haven’t seen anything which suggests they are going down the path you refer to here. A local client they own is their differentiator over the browser, why would they abandon that?

Re: Web IDE Beta

#176

Post by morelisp »

azalemeth wrote: post #88
morelisp wrote: post #43

Earlier quoted context omitted.

I see your profile says you’re in your early 20s, so I kind of understand the question but also I’ll be blunt: yes, there will be another text editor. 90% of the tools you use today will be gone by the end of your career.

And the remainder will be called things like vim, emacs, awk, and sed ;-)

Even awk is slowly but surely on the way out at this point... sed probably has another strong decade though.

Re: Web IDE Beta

#177

Post by sebular »

tlonny wrote: post #166
andrew_ wrote: post #115

Earlier quoted context omitted.

The way that VS Code is spreading, and the stranglehold Microsoft has on development and direction of the product, give me very strong IE4/5/6 vibes. I really hope some of the open source alternatives that aren't corporation-controlled gain traction over the next year.

I moved from vim to VS code as I found the vim IDE experience slightly lacking. Recently I've found myself getting more and more fed up with how sluggish VS code feels. With the push from a friend, I tried neovim with the requisite LS plugins and I'm never going back. It's lightning fast and has feature parity (at least the ones I use) with VS Code. Its a bit of a bitch to setup, but there are preconfigured solutions…

NvChad is excellent. I recently finished converting my older .vimrc-based configuration to an entirely lua-based one on top of the base NvChad setup and it‘s just perfect.

Re: Web IDE Beta

#178

Post by morelisp »

joshmanders wrote: post #165
pionar wrote: post #148

Earlier quoted context omitted.

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.

You're just being pedantic now. VSCodium exists because VSCode is FOSS. Your complaint is with the binary that Microsoft ships, not with the codebase.

Sounds to me like they've got sufficient fanboy mindshare to move fully into "extinguish" soon!

Re: Web IDE Beta

#179

Post by dijit »

joshmanders wrote: post #165
pionar wrote: post #148

Earlier quoted context omitted.

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.

You're just being pedantic now. VSCodium exists because VSCode is FOSS. Your complaint is with the binary that Microsoft ships, not with the codebase.

Parents complaint is that paying lip service to FOSS is exactly the "extend" part of "Embrace, Extend, Extinguish".

A mantra that was famously internally coined at Microsoft[0], and was found during anti-monopoly proceedings.

As such they will always be looked at skeptically when adding proprietary things to open source things.

[0]: https://en.wikipedia.org/wiki/Embrace,_extend,_and_extinguis...

Re: Web IDE Beta

#180

Post by dvko »

tlonny wrote: post #166
andrew_ wrote: post #115

Earlier quoted context omitted.

The way that VS Code is spreading, and the stranglehold Microsoft has on development and direction of the product, give me very strong IE4/5/6 vibes. I really hope some of the open source alternatives that aren't corporation-controlled gain traction over the next year.

I moved from vim to VS code as I found the vim IDE experience slightly lacking. Recently I've found myself getting more and more fed up with how sluggish VS code feels. With the push from a friend, I tried neovim with the requisite LS plugins and I'm never going back. It's lightning fast and has feature parity (at least the ones I use) with VS Code. Its a bit of a bitch to setup, but there are preconfigured solutions…

Seconded. Neovim with their built-in LSP is so good! Was a happy VSCode user for years but not very comfortable with how they’re starting to push more and more proprietary pieces, so started looking for alternatives. Neovim fits the bill perfectly.

Helix is another one to watch. Not quite at Neovim’s level and may need some reprogramming of the vim muscle memory but definitely promising!

Post reply on HN