3 ms·

That's a lot of words compared to "Download binary from server. Run it"

by mhh__ 2y ago

zahlman 2y ago
Sometimes it takes a lot of words to debunk a misconception. What you initially said didn't have anything to do with setup effort, but also there is quite little setup effort actually described here.
- mhh__ 2y ago
  There is nothing to debunk, my original comment was correct. It's useful to have tooling that doesn't rely on carting around a bunch of python stuff.
  - zahlman 2y ago
    In that case I have absolutely no idea what point you're trying to make. What coupling are you talking about, and why is it a problem? What do you mean by "carting around a bunch of Python stuff", and why and how is it "useful" to avoid that?
    - kstrauser 2y ago
      Not the person you’re replying to, but if I’m write Python 3.13, and my linter requires Python <= 3.11, now I have to install 2 Pythons. It’s nice to not have to consider that case at all.
      - zahlman 2y ago
        As a developer, with a real use case for these tools, I plan to support multiple Python versions anyway, and have them all installed for testing purposes. There only needs to be one actual installation of each; everything else is done through venvs, which are trivial to spin up.
    - mhh__ 2y ago
      If I want to ship this to colleagues (some of whom probably won't know what a venv is but do have to write python every now and again) I only have to worry about a single binary. Getting consistent python environments on peoples machines, particularly on windows, is expensive (salary).
      - zahlman 2y ago
        >If I want to ship this to colleagues then they don't need your dev tools. >won't know what a venv is but do have to write python every now and again In practical terms, you have to understand what a venv is in order to be a Python developer, for the same reason you have to understand environment variables to do anything serious in the shell. Learning the fundamentals is a one-time cost.

That's a lot of words compared to "Download binary from server. Run it"

by mhh__ 2y ago

That's a lot of words compared to "Download binary from server. Run it"

Sometimes it takes a lot of words to debunk a misconception. What you initially said didn't have anything to do with setup effort, but also there is quite little setup effort actually described here.

mhh__ 2y ago
There is nothing to debunk, my original comment was correct. It's useful to have tooling that doesn't rely on carting around a bunch of python stuff.
- zahlman 2y ago
  In that case I have absolutely no idea what point you're trying to make. What coupling are you talking about, and why is it a problem? What do you mean by "carting around a bunch of Python stuff", and why and how is it "useful" to avoid that?
  - kstrauser 2y ago
    Not the person you’re replying to, but if I’m write Python 3.13, and my linter requires Python <= 3.11, now I have to install 2 Pythons. It’s nice to not have to consider that case at all.
    - zahlman 2y ago
      As a developer, with a real use case for these tools, I plan to support multiple Python versions anyway, and have them all installed for testing purposes. There only needs to be one actual installation of each; everything else is done through venvs, which are trivial to spin up.
  - mhh__ 2y ago
    If I want to ship this to colleagues (some of whom probably won't know what a venv is but do have to write python every now and again) I only have to worry about a single binary. Getting consistent python environments on peoples machines, particularly on windows, is expensive (salary).
    - zahlman 2y ago
      >If I want to ship this to colleagues then they don't need your dev tools. >won't know what a venv is but do have to write python every now and again In practical terms, you have to understand what a venv is in order to be a Python developer, for the same reason you have to understand environment variables to do anything serious in the shell. Learning the fundamentals is a one-time cost.