You are missing my point. In your example, you mention bazel, but I've never seen any Java projects using it in the wild. This is very specific to Google and probably won't be selected by most companies. Maintaining an ecosystem that supports a wide variety of workflows is very hard, even more so in the cloud. This is why I am very sceptical that coding online is the future.
Another thing I've found annoying with web-based IDE's is that hotkeys of the browser itself can conflict with your terminal ones (ie, readline defaults). This is a fairly minor issue though.
You are missing my point. In your example, you mention bazel, but I've never seen any Java projects using it in the wild. This is very specific to Google and probably won't be selected by most companies. Maintaining an ecosystem that supports a wide variety of workflows is very hard, even more so in the cloud. This is why I am very sceptical that coding online is the future.
Another thing I've found annoying with web-based IDE's is that hotkeys of the browser itself can conflict with your terminal ones (ie, readline defaults). This is a fairly minor issue though.
I am not saying Google's tech was best for most companies, but it was very productive for one workflow.
We aim to do this for fullstack apps written in TypeScript.
Fully agree with the hotkeys, its annoying but yeah..minor.