Decide on the development environment #5
Replies: 2 comments 1 reply
-
|
I am bullish on cloud-native development now. GitHub Codespaces just became generally available. You can develop in a CPU-backed environment for up to 60 hours a month. I expect there to be really nice integrations with GitHub Actions as well. GPU-backed Codespaces are not GA, but you can ask for access here. I expect them to become GA by the time the next class is taught. Alternatively, we could use Modal. I've found the development experience very smooth -- e.g. you can run a IPython REPL inside of your programs executing on the cloud with just a single (non-Modal) line of code. In either case, but especially with Codespaces, we'll want to make the best possible use of |
Beta Was this translation helpful? Give feedback.
-
|
I really like the idea of using containers: it will be easier to move from
I am a bit unsure. On one side, I understand that cloud development tools (like Codespaces) are very handy. On the other, when looking into these tools, I am often worried about how much the final cost of usage would be, and I end up developing locally. (At least at the start, when writing code and running small tests, local laptops are often enough.)
If we go with containers, I am not sure with could fully support M1 Mac. For example, is there a way to connect to their GPU via Docker? (But as a M1 user, I hope that they will be supported at some point 😇 )
I have used Colab mostly to quickly interact with a public notebooks (e.g. the course labs). I never used it for 'full' development. My opinion is that it should not be priority num 1. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Beta Was this translation helpful? Give feedback.
All reactions