In Python the IDE doesn't matter as much, because if the support is bad, you can always fall back on pdb.
In fact, I often use pdb anyway because it is sometime just quicker to run, and the code execute faster under it. Also, being able to execute any python code in a shell like env is super nice, and the concept of having commands instead of looking for a button has the same pros/cons than the cli.
In the extreme, yes, and low resolution on large screens are also difficult to read. Viewing distance is also a factor. You always need to find a balance.
For those who are wondering what is the benefit over pip freeze: pip freeze dumps you entire venv, while pip compile gets project dependancies, and infer the requirements file from that.
I'm not sure I get it -- if you had your core dependencies in setup.py / setup.cfg / pyproject.toml (for development) and then pip freeze (for creating a highly reproduced venv for applications), would that be similar?
Why would one want to infer the requirements file? Would that be like `pip list --not-required --format-freeze`?
- you set it up correctly
- your entire stack is compatible from end 2 end
- there is now weird thing with map files
- you don't dev using firefox
It's a lot of if.