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

221–230 of 258 posts

Re: Web IDE Beta

#221

Post by milohax »

jamisonbryant wrote: post #147
john_cogs wrote: post #142

Earlier quoted context omitted.

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…

GitLab Support team member here.

As a work-around, if you know the name of the existing branch you want to switch to, you can change the URL in your browser's location bar for the IDE. Here's the URL format:

    https://gitlab.com/-/ide/project//[/...]/edit//-/
This will re-load the IDE on the different branch.

You can also switch branches in the GitLab UI's Files view, before launching the Web IDE with the "Web IDE" button (or the `.` shortcut).

Also pressing "Web IDE" from an MR in GitLab will open that MR's branch in the Web IDE.

So it depends upon your workflow currently, but I agree it will be nice to be able to swap within the IDE itself later (also when the GitLab Flow extension is added).

The built-in git support in Code is already an improvement over the old Web IDE's Stage/Commit workflow, IMHO, and after the first load, the new Web IDE also loads faster than the old one, for me at least.

Re: Web IDE Beta

#222

Post by rileyphone »

yjftsjthsd-h wrote: post #173
azalemeth wrote: post #88

Earlier quoted context omitted.

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:)

Lindy effect.

Re: Web IDE Beta

#223

Post by zachruss92 »

jenny91 wrote: post #220

I wish Gitlab would just fix up their existing product instead of increasing the surface area. Every month they put out a security release that often contains a couple of "high severity" bugs and every couple of months there's a "critical" one. And they're not rocket science either, simple auth check bypasses and so on. Clearly something's not going right in the culture if you have multiple critical security bugs eve…

I got burned so many times by GitLab I can't in good conscience use them anymore. I always try to use an OSS product when I can, but I literally lost a client a few years back because we couldn't do a deploy because GL was down. For now I use GH for critical projects and a self hosted Gitea instance when it's not super critical.

Re: Web IDE Beta

#224

Post by AlexErrant »

zachruss92 wrote: post #223
jenny91 wrote: post #220

I wish Gitlab would just fix up their existing product instead of increasing the surface area. Every month they put out a security release that often contains a couple of "high severity" bugs and every couple of months there's a "critical" one. And they're not rocket science either, simple auth check bypasses and so on. Clearly something's not going right in the culture if you have multiple critical security bugs eve…

I got burned so many times by GitLab I can't in good conscience use them anymore. I always try to use an OSS product when I can, but I literally lost a client a few years back because we couldn't do a deploy because GL was down. For now I use GH for critical projects and a self hosted Gitea instance when it's not super critical.

To be fair, Github actions has a spotty record as well. https://www.githubstatus.com/history

Re: Web IDE Beta

#225

Post by dmitriid »

bastawhiz wrote: post #213
dmitriid wrote: post #137

Earlier quoted context omitted.

> It's never been my experience that a full IDE is better for dynamic interpreted languages. IntelliJ IDEs are very good at figuring out dynamic languages, but on top of that they also know a lot of tooling and frameworks. So even if you have dynamic Python, but use it in Django, IDEA/PyCharm will be able to give you completions, code navigation, and refactoring just by the virtue of knowing what goes where in Django…

I get that from vscode and pylance/mypy already. I get the same thing with vscode and sorbet for Ruby. Why would I go through all the trouble of using IntelliJ for that?

For everything listed in the "Working with source code" menu: https://www.jetbrains.com/help/pycharm/working-with-source-c... (and others like https://www.jetbrains.com/help/pycharm/web-frameworks.html)

Some of it made its way into VS Code, but many things definitely didn't (because they require more than just LSP and reuire someone to write a bunch of analysis tools for the python integration).

Re: Web IDE Beta

#226

Post by choward »

zachruss92 wrote: post #223
jenny91 wrote: post #220

I wish Gitlab would just fix up their existing product instead of increasing the surface area. Every month they put out a security release that often contains a couple of "high severity" bugs and every couple of months there's a "critical" one. And they're not rocket science either, simple auth check bypasses and so on. Clearly something's not going right in the culture if you have multiple critical security bugs eve…

I got burned so many times by GitLab I can't in good conscience use them anymore. I always try to use an OSS product when I can, but I literally lost a client a few years back because we couldn't do a deploy because GL was down. For now I use GH for critical projects and a self hosted Gitea instance when it's not super critical.

One of the benefits of gitlab is you can host it yourself. Github has also had outages.

Re: Web IDE Beta

#228

Post by shkkmo »

taeric wrote: post #200
shkkmo wrote: post #188

Earlier quoted context omitted.

This doesn't really match since the "Embrace" part is different. The classic formula was "embracing" an established standard, making proprietary extensions to that standard, then using the adoption of those proprietary extensions to extinguish the original standard's market share. In this case, Microsoft didn't embrace an existing code base or standard, they made one and open sourced it. What would the analagous "ext…

It is quite easy to see that the "embrace" is to release a core into the open source world. They embraced the idea of open source and released something, they extended the user base into the world of the non-free option. The thinking is if they can get a critical mass of folks onto the option that is non-free, they will extinguish the free option by no longer supporting it. And this is not much different from the thi…

> The thinking is if they can get a critical mass of folks onto the option that is non-free, they will extinguish the free option by no longer supporting it.

I assume you mean "non-free" as in speech, not beer, since VSCode is free. Hasn't that "critical mass" been the case since day one? I can't imagine that VSCodium built binaries have ever had more than a tiny fraction of the user-base of VSCode? Thus I don't see how "Extinquish" plays a role here.

I still think it makes more sense to think of the strategy as more akin to the FOSS-washing / freemium models used by many companies.

Re: Web IDE Beta

#229

Post by shkkmo »

otabdeveloper4 wrote: post #199
shkkmo wrote: post #188

Earlier quoted context omitted.

This doesn't really match since the "Embrace" part is different. The classic formula was "embracing" an established standard, making proprietary extensions to that standard, then using the adoption of those proprietary extensions to extinguish the original standard's market share. In this case, Microsoft didn't embrace an existing code base or standard, they made one and open sourced it. What would the analagous "ext…

> What would the analagous "extinction" bere here? Look at Android and how it is almost impossible to de-Google it for a live demonstration. (I don't think there is a market for developer tools, though.)

There are several android distros that provide support for a de-googled installation. Calling it "impossible" seems like a bit of a stretch, though there are definitely limitations, even with microg installed.

I do think that the VSCode model is much more similar to the Android model (though Android is a more extreme version of the model) than either is to the "Embrace, Extend, Extinguish" model.

Re: Web IDE Beta

#230

Post by another_devy »

jdthedisciple wrote: post #227
coreyog wrote: post #163

A buddy sent me this article a few days ago: https://ghuntley.com/fracture/ If I hadn't read it, I might think Gitlab incorporating vscode was a good thing.

Seriously no time to read this. What's the TL;DR?

TL;DR (meta phrased)

Microsoft is forking VSCode open source community by split licensing for source code and and official build of VSCode. If you build by yourself you can’t connect to VSCode is marketplace.

This allows them to fully control VSCode telemetry and reporting along with use on platforms such as Gitpod. It’s similar to how Apple controls apps on iPhone and in turn control how much you need to pay them if you earn money on it.

In long run everything going on cloud and SaaS/ PaaS platform holding the keys to developer tooling gate such as VSCode, Microsoft has unfair advantage over other competitors and still keep benefits of OSS

Post reply on HN