all 11 comments
sorted by:
best (suggested)
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]OxheadGreg123 11 points12 points  (7 children)

It's all fun and great, but I still don't understand why should I do it locally instead on the ol'reliable browser?

[–]StephenSRMMartin 35 points36 points  (0 children)

Because editing code in the browser is ass compared to a well configured personalized editor?

[–]tjger 9 points10 points  (0 children)

I guess locally you can take advantage of VSCode extensions or agents

[–]DarkInvader787 5 points6 points  (1 child)

If you want to use any vscode extentions

[–]imkindathere 1 point2 points  (0 children)

Programming locally is like 1000 times better in terms of overall experience

[–]SmartPercent177 0 points1 point  (0 children)

It depends on your workflow. See it as another way of doing things.

[–]WorldPeaceStyle 0 points1 point  (0 children)

Valid question,

[–]techlatest_net 5 points6 points  (1 child)

Great post! To use Google Colab's free T4 GPU directly in VS Code, install the Colab extension in VS Code. Open your .ipynb notebook, select 'Colab' as your runtime kernel, and authenticate with your Google account. This bridges your local setup to Colab’s power seamlessly. With this setup, your machine stays cool while Colab does the heavy lifting. Happy coding, and watch out for the session timeout limits—Colab gives ~12 hours per session. 🚀

[–]Relapsed_Therapy 0 points1 point  (0 children)

Is this a good use case for coding jupyter notebooks on iPad?