Hell no, no way I'd trust Google with my code. Personal or otherwise. Let me guess this would work only in Chrome.

What if your dev experience was entirely in the cloud?

What if your dev environment could disappear completely one day when we get bored of maintaining it after it doesn't immediately displace github?

What if your dev experience was entirely in the cloud?

No. Just no.

Fuck no.

Cringe. Not everything needs to be offloaded to someone else's computer.

And frankly, why would I pay some sort of fee (which they will eventually charge, even if they don't right now) for the "privilege" of having rustc fight for execution time on a vCPU somewhere in California?

Every day that passes I lean further towards pursuing a career in embedded.

These days, launching applications means navigating an endless sea of complexity.

• Meta + D
• "vsco"
• Enter

Damn, I'm exhausted, why does launching an application have to be so hard?

Even if it's very cool, the problem I have with newer google products is that they might just kill it at any time, even if it's successful.

I don't see how this could be positive for any Software developer in the long run. I totally see how this could be positive for CEO/CTO, Project Managers, in the long run, and I see a few short term advantages for Software developers.

Let's be clear, I saw that coming since Microsoft bought Github, and I am scared by the direction this is taking. The end goal is to move more and more control and power to non-software people about Software development.

By forcing every developer to not use their own tools this will have a lot of advantage for CEO/CTOs but this is terrible for software developers:

1. telemetry: they will try to find a formula to assess who are the best performer in a team. And as with SEO, any formula could be gamed, the best at this game, will not be the best software developers, but the one that will learn how to cheat.
2. global team tooling enforcement: vim vs emacs etc... ? Forget about it, the only way to work on a project will be via this unique allowed editor.
3. assets protection: impossible to download the code on your local computer to use external tools on it. The only way to have analysis tools will be via these "allowed" analysis tools. This will make code analysis and experimentation a lot more difficult.
4. Locked by promoting vendor-specific applications. As you will focus to make your code/app/product work only for Google Cloud for example, you will naturally use Google-Cloud-only features that will make your code difficult (or impossible) to move to another Cloud provider, or god-forbid, host your product on a non-cloud or private made cloud.

And I can think of other possible drawbacks but my comment is already long enough.

I have a simple method for deciding whether or not to use something.

• Is it a “cloud service”?
• Is it made by google?

If either of these is a yes, I look for something else

So, like 18 months before this gets added to the Google graveyard?

No.

Google probably want that sweet, sweet development stages of the code, every interaction at debugging, documentation editing, everything, to train their AI.

You know they'll be saving every line of code and analyzing it and feeding it into their ML models.

Fuck that. Anything I do is staying right here with me unless it's something I choose to share on GitHub.

This is wrong on so many levels, I cannot fathom where I could start talking about it.

• private us company
• feeding their ai just to eventually negate myself the chance of those small side projects that pay small money
• us company
• chromium browsers
• governments shouldn't allow for source code, as trivial as it may be, to be centralized in another nation
• us corporation
• google (in my experience) devastating ux, ui, docs
• go and try to use aws, azure, you name it services (this ip/fqdm doesn't seem to be part of google services! would you like to try out or service? start with our free plan with the performance of a C64, and choose to upgrade whenever you want!)
• us based private corp
• chromium browsers
• this functionality is now deprecated (rewrite all of your f**** code, you absolute dumbass...) Ugh...

I do think it solves an interesting problem where you’re working on your desktop and decide to move to your laptop and continue working on the same codebase, but don’t want to commit early so you can pull down the changes to your laptop.

You can just push the changes to a different branch and then merge it to your normal feature branch later. Takes like 5 seconds.

"Hey you guys, come and use our totally free online thing. We promise we won't use anything you do for our own gains! Pinky swear!"

Cloud is a plague.

Mmh. Don't like that

Things have been headed this way for a loooong time. That said, unless I can self-host something like this, I'm not interested.

I might be open to the idea, but it would need to be a trustworthy company that doesn't cancel stuff left and right. An ide would be too annoying to switch constantly to take this risk.

The sad truth is that people are stupid enough to use this.

I do think it solves an interesting problem where you’re working on your desktop and decide to move to your laptop and continue working on the same codebase, but don’t want to commit early so you can pull down the changes to your laptop.

This has been a solved problem for decades. SSH.

If I'm not able to self-host it a la VS Codium, then it's very much a honeypot.

Yummy yummy give me your codei !!

We don't need everything in the cloud or in a browser

This is a play against VSCode and the developer moat MS/GitHub have built right? In which case, go at it I guess.

The Shell -> Mainframe style IDE has been coming for a while. And makes some sense, however much of a local app person you are. I’m kinda surprised Google hadn’t made a move yet. On which, it’s suspicious that this is probably driven or associated with AI.

So cancer + a different form of cancer = ...?

I really don't get why you want an editor to be based on DOM, it feels just like sluggish ... cancer...