It is their right to ban any use they want. Colab is an awesome service, so much so that I seldom use my at-home GPU rig.
As consumers we can use or not use platforms like Google, Twitter, etc. as we like, or not.
Colab’s ban will be good for small 3rd party GPU cloud providers and that is a good thing. Same thing with Twitter: in the last month there is now better material on Mastodon.
It's my right to yell at anyone who accidentally steps off the sidewalk into my yard, but that right doesn't invalidate criticism and judgments I receive in response to my actions.
So I really dislike Jupyter, and I've tried using this[0] before to ssh into Colab and do work in a terminal setup.
You have to be careful to back up your code frequently (what I did was push to Github) since your ssh session goes away when your "kernel" (or whatever your colab session is called) goes away. You wouldn't have this worry if you were just using the web interface, since the code is always saved.
I'd imagine that, if you want to use VSCode, it's remote editing features, which I keep on hearing a lot about, would come in handy to edit over ssh!
VS Code can render Jupyter notebooks (it connects to the kernel). I don't know if "use colab from VSCode" means connecting your VS Code to a remote colab kernel.
As consumers we can use or not use platforms like Google, Twitter, etc. as we like, or not.
Colab’s ban will be good for small 3rd party GPU cloud providers and that is a good thing. Same thing with Twitter: in the last month there is now better material on Mastodon.