3 ms·
I've switched to Python a little while ago for the following use-cases, and couldn't be happier: - Non-performance-critical command line tools for game-data ex
by flohofwoe 11y ago
I've switched to Python a little while ago for the following use-cases, and couldn't be happier:
- Non-performance-critical command line tools for game-data export-pipelines that I previously wrote in C/C++: Python code is usually more compact, and everything I ever needed is in the standard library. If performance is critical I still prefer python to call out to minimal C or C++ tools which do the heavy-lifting.
- Replace native shell-scripts and Windows batch files with portable python scripts that run on Windows, Linux and OSX.
- Stitching together 3D content-creation-tools and command line tools, most DCC tools of have become python-scriptable in recent years.
- Code generation for C/C++ and shader code.
These are all very pragmatic and simple things, I don't care whether my python scripts are 'pythonic' or elegant, and I don't care about the 2 vs 3 debate. Python gets the job done, works everywhere, and I enjoy writing it because of its friendly syntax and powerful standard library.