3 ms·

The final response from the team at Amazon is incredibly gracious considering how condescending and entitled almost all the other comments are. Please don’t be

by enneff 5y ago

The final response from the team at Amazon is incredibly gracious considering how condescending and entitled almost all the other comments are. Please don’t be like those commenters.

hodgesrm 5y ago
The first note in the issue was also straightforward and clearly reasoned. Aws-cli is a lot more than a Python script. It's used by hundreds of thousands if not millions of developers and admins. I completely understand their desire to avoid being caught up in the complexity of Python package management.
Tainnor 5y ago
You can call it entitled, but: - Lots of people don't have a choice if they want to use AWS, someone in the business decided it for them - AWS is not some non-profit open source pet project but actively tries to pull as many devs and companies as possible into their ecosystem - Breaking users' workflows is always going to cause issues. AWS CLI v1 was distributed on pypi, lots of people had already built workflows around that. - It is my understanding that for some people / use cases (e.g. using pyenv), having aws cli being tied to the system python causes significant issues for some reason (I can't remember exactly why, but a coworker struggled with this for days). It might have something to do with the PYTHONPATH, not sure. - The whole response from Amazon reads as "we know what's best for you" and frankly, I find that kind of attitude (which seems to be increasing among big corps) infuriating. Large tech companies already have way too much control over the ways we build software, it would be nice if they didn't also control our workflows. Full agreement that many people in that GitHub issue were not being constructive and behaving childishly, but I still believe that Amazon deserves criticism here.
- res0nat0r 5y ago
  Aws cli v2 installs it's own self contained python so it shouldn't be tied to any system install. Frankly it's good to see devs not ceding to the internet rage mob. I remember before aws hired the main guy behind boto and I had to install 10 different tar.gz tools from 10 different aws teams and install all of them and setup 20 different env variables. Running their installer isn't difficult and I've included it in our docker and ami builds easily. If you want a fixed version, download whatever from their repo and mirror it to your internal storage and you can always install from there and ensure you're running the exact version you like. This response (from a year ago) seems perfectly reasonable and explains in detail a good number of reasons why they aren't using pip: https://github.com/aws/aws-cli/issues/4947#issuecomment-586046886 https://github.com/aws/aws-cli/issues/4947#issuecomment-5860...

by enneff 5y ago

The final response from the team at Amazon is incredibly gracious considering how condescending and entitled almost all the other comments are. Please don’t be like those commenters.

hodgesrm 5y ago

The first note in the issue was also straightforward and clearly reasoned. Aws-cli is a lot more than a Python script. It's used by hundreds of thousands if not millions of developers and admins. I completely understand their desire to avoid being caught up in the complexity of Python package management.

Tainnor 5y ago

You can call it entitled, but: - Lots of people don't have a choice if they want to use AWS, someone in the business decided it for them - AWS is not some non-profit open source pet project but actively tries to pull as many devs and companies as possible into their ecosystem - Breaking users' workflows is always going to cause issues. AWS CLI v1 was distributed on pypi, lots of people had already built workflows around that. - It is my understanding that for some people / use cases (e.g. using pyenv), having aws cli being tied to the system python causes significant issues for some reason (I can't remember exactly why, but a coworker struggled with this for days). It might have something to do with the PYTHONPATH, not sure. - The whole response from Amazon reads as "we know what's best for you" and frankly, I find that kind of attitude (which seems to be increasing among big corps) infuriating. Large tech companies already have way too much control over the ways we build software, it would be nice if they didn't also control our workflows. Full agreement that many people in that GitHub issue were not being constructive and behaving childishly, but I still believe that Amazon deserves criticism here.

res0nat0r 5y ago
Aws cli v2 installs it's own self contained python so it shouldn't be tied to any system install. Frankly it's good to see devs not ceding to the internet rage mob. I remember before aws hired the main guy behind boto and I had to install 10 different tar.gz tools from 10 different aws teams and install all of them and setup 20 different env variables. Running their installer isn't difficult and I've included it in our docker and ami builds easily. If you want a fixed version, download whatever from their repo and mirror it to your internal storage and you can always install from there and ensure you're running the exact version you like. This response (from a year ago) seems perfectly reasonable and explains in detail a good number of reasons why they aren't using pip: https://github.com/aws/aws-cli/issues/4947#issuecomment-586046886 https://github.com/aws/aws-cli/issues/4947#issuecomment-5860...