Earlier quoted context omitted.
Google is weird, they want to conquer Cloud market but they dont do anything like VSCode or Github in dev community. In 10 years Google regret not buying Github.
Google had a viable GitHub competitor at one point. But they let it languish and then shut it down. It's a familiar story.
The Future of the Gitlab Web IDE
121–130 of 168 posts
Re: The Future of the Gitlab Web IDE
#122> These lightweight changes make up the vast majority of the Web IDE usage Imho, that’s Web Text Editor. It’d be helpful to not mix junior an “editor” with an “IDE”. If someone at Gitlab is listening then it’d actually be a differentiator to make an IDE (and charge for it) to also those platforms where having a beefy laptop becomes a requirement (eg Android) and developers on those platforms, or a lot of them like me…
Re: The Future of the Gitlab Web IDE
#123Job titles seem really important to the content here > In this video Paul Slaughter, Staff FE Engineer, walks Eric Schurter, Senior Product Manager
They just erased 4 years of work by simply replacing it with a superior and open-source tool, VS Code. They’ve gotta justify their existence somehow.
Here's all the justification you need. Work doesn't have any value by itself.
Re: The Future of the Gitlab Web IDE
#124Earlier quoted context omitted.
Google had a viable GitHub competitor at one point. But they let it languish and then shut it down. It's a familiar story.
What was that called?
Re: The Future of the Gitlab Web IDE
#125> These lightweight changes make up the vast majority of the Web IDE usage Imho, that’s Web Text Editor. It’d be helpful to not mix junior an “editor” with an “IDE”. If someone at Gitlab is listening then it’d actually be a differentiator to make an IDE (and charge for it) to also those platforms where having a beefy laptop becomes a requirement (eg Android) and developers on those platforms, or a lot of them like me…
Re: The Future of the Gitlab Web IDE
#126It's interesting to me that GitLab is adopting a Microsoft product (VS Code) and Microsoft owns a significant competitor in GitHub. Nothing intelligent to say about that other than to wish I'd been a fly on the wall for the discussions about that. > Next, we asked ourselves the question: Do we want to continue to invest in implementing custom features for the Web IDE that ultimately deliver the same value as those al…
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.
And yet they failed. Remember Atom[1] or Brackets[2]? I'm sure they are still used by a lot of people. But it was interesting to see Microsoft grow VS Code so fast in popularity. My vague notion is that addressing developer pain points early and providing first party plugins for popular ecosystems gave them an edge.
Re: The Future of the Gitlab Web IDE
#127It's interesting to me that GitLab is adopting a Microsoft product (VS Code) and Microsoft owns a significant competitor in GitHub. Nothing intelligent to say about that other than to wish I'd been a fly on the wall for the discussions about that. > Next, we asked ourselves the question: Do we want to continue to invest in implementing custom features for the Web IDE that ultimately deliver the same value as those al…
Yeah, especially when they could use something like Theia[0], which I believe was built for this kind of purpose? They both still use Monaco under the hood AFAICT. I'd be interested to know if they considered it and decided not to use it for some reason. 0: https://theia-ide.org/
We have considered Theia in the past. Here are a couple of related epics/issues:
Re: The Future of the Gitlab Web IDE
#128> These lightweight changes make up the vast majority of the Web IDE usage Imho, that’s Web Text Editor. It’d be helpful to not mix junior an “editor” with an “IDE”. If someone at Gitlab is listening then it’d actually be a differentiator to make an IDE (and charge for it) to also those platforms where having a beefy laptop becomes a requirement (eg Android) and developers on those platforms, or a lot of them like me…
It would be great if you could share your insights and feedback on the public epic for the strategy for remote development: https://gitlab.com/groups/gitlab-org/-/epics/7419
Re: The Future of the Gitlab Web IDE
#129Maybe I'm getting old, but I don't want to do all development-related tasks in my web browser. As a software engineer, I want local control, where an internet connection is optional. I want to be able to experiment with the software in various local setups. I just don't get why Gitlab thinks this is a good idea worth a huge amount of engineering effort. Are people really clamoring for this feature?
> Are people really clamoring for this feature? Yes. Because local development environments (at least for the languages I work with, Python and JavaScript) break ALL THE TIME. With 20+ years of experience I can just about keep my own laptop ticking over - but it takes work, and every time I mentor a new learner this is the number one sticking point. The browser-based cloud IDE experience, where it doesn't matter what…
as an industry we keep fighting nature and not working with nature. how much money has been spent trying to optimize python, ruby, js build tools / environments etc. you wouldn't need docker, web ide's and all the other crap if a language could ship a single executable. if we moved away from dynamic linking that's linked to the 80s thinking of limited storage to static linking.
whereas going back to saner defaults would've saved much of this headache.
Re: The Future of the Gitlab Web IDE
#130Earlier quoted context omitted.
What IDE do you 'own'?
I guess that OP is talking about having the IDE/compiler/etc binary on their computer and not having to rely on any external service to work.
[0] https://docs.gitlab.com/ee/user/project/repository/vscode.ht...
[1] https://about.gitlab.com/blog/2021/05/20/vscode-workflows-fo...