Do it. Never look back!
Seriously, just leave Matlab in the ditch on the side of the road.
My wife (currently completing her PhD in pattern recognition and deep learning) has half her code in MatLab and at least half the time-cost of working on that portion can be attributed to hassles with licensing.
The other half is in Python.
She can just work on the Python half, wherever she is, even without a connection. She can easily punt it to the powerful GPU-packing machines in her lab (or, when they're not free, my gaming PC with its 1080ti) to train models overnight. She can even do this remotely by simply issuing a `git pull` from Jupyter's terminal emulator in a web browser -- that's all it takes and the notebook that acts as a pretty `main()` method is ready to run. Heck, she can navigate to the little Gentoo server that lives on the top of a cupboard in our house, patch bugs in GitLab's browser-based editor, commit from the web interface and restart an experiment all from her phone while sitting on a train!
It's almost like she owns her own work, in Python.
And, if she copies some Python snippets off the web (StackOverflow, reddit, GitHub or Kaggle, for example), the license doesn't belong to MathWorks. Read the terms of MatLab's community forums; all code posted becomes property of MathWorks automatically! (That's proper arrogance and arseholery.)
MatLab does only one thing well: it visualises data in a way that no open-source tool does. When you're stopped on a breakpoint or looking at variables in your session, drilling down into them, graphing them, pretty-printing them and watching them in MatLab makes for a better experience than any other.
If open-source tools like Jupyter were to implement the fancy data visualisation tricks that MatLab provides, I'm sure that MathWorks would be reduced to changing their corporate font, refreshing their logo, updating their branding and patent-trolling to stay alive -- and good riddance!