6 ms·
One weird thing about the language, which seems contrary to this "most productive language" claim, is that it seems a bit complicated to use normal version cont
by dsizzle 5y ago
One weird thing about the language, which seems contrary to this "most productive language" claim, is that it seems a bit complicated to use normal version control https://mathematica.stackexchange.com/questions/26174/what-are-the-recommended-settings-for-git-when-using-with-mathematica-projects/26180#26180 https://mathematica.stackexchange.com/questions/26174/what-a...
- Smaug123 5y agoVersion control is very easy as long as you're not versioning notebooks. A `.m` file is just plain text.
- gdelfino01 5y agoThe language is version control friendly, the notebooks are not. You explore and document using notebooks (.nb) and if your stuff get serious you should move the source code to a package (.wl or .m) which is just plain text file which is nice for version control.
- dsizzle 5y agoRight, but I mean it's a notebook-based language/environment so they seem hard to uncouple. Just looking at the link I posted it seems a little complicated. Have you used Mathematica in a team situation?
- scoopertrooper 5y agoYou'd run into the same problem with Python notebooks. For a lot of data scientists out there, Python is a notebook based language. The Stackoverflow thread had a few other interesting ideas beyond discarding the notebooks entirely.
- dsizzle 5y agoRight, but no one is claiming Python notebooks is the world's most productive way to work!