3 ms·
Do we really want to develop in the cloud? My gut says no. I have no real opinion about that, but seems worth investigating. Is anybody working with a proper de
by RamblingCTO 4y ago
Do we really want to develop in the cloud? My gut says no. I have no real opinion about that, but seems worth investigating. Is anybody working with a proper dev environment (no, sorry, a small react-only project doesn't cut it, I'm talking jvm driven, ran by docker kind of thing) in the cloud here?
- kajecounterhack 4y agoYeah, as another commenter mentioned, all Google SWEs have developed in the cloud for a long time. It allows you to write, run, and test code performantly on any computer with a browser. Some of OP's wishlist are realities at Google. E.g. - When I compile code, I want to fire up 1000 serverless container and compile tiny parts of my code in parallel. - When I run tests, I want to parallelize all of them. Or define a grid with a 1000 combinations of parameters, or whatever. Build systems, testing infra, and cloud editing all need to be there for the magic to happen. When your cloud editor supports distributed builds & testing infra, and can be used by anyone, life is really good. FWIW widely available cloud editing is also getting good with VSCode + LSP, if you don't want to pay Replit. Getting Bazel to do distributed builds instead of local builds is really annoying tho.
- RamblingCTO 4y agoThank you! So I think for us the only attractive thing is to have cloud runners for our sadly very resource-heavy tests.