←back to thread

320 points willm | 6 comments | | HN request time: 0.993s | source | bottom
1. dekhn ◴[] No.45106670[source]
It added intrusive- codebase-wide- functionality that more or less could have been done with other (thread-based) approaches.

AWSCLI was broken for over a year- we had to do a ton of work to deal with the various packaging issues.

Don't break userspace.

replies(1): >>45109218 #
2. AtlasBarfed ◴[] No.45109218[source]
Why was awscli written in python? Bad decision to begin with.

Hey! We have a product that we clearly want to release worldwide. Let's build it on something that doesn't have Unicode. Or any real threading. And is slow as hell.

You picked a platform that was going to have to break user space.

At least it wasn't JavaScript

replies(3): >>45110182 #>>45111808 #>>45111873 #
3. fzzzy ◴[] No.45110182[source]
Doesn’t have Unicode? What the heck?
replies(1): >>45111861 #
4. mdaniel ◴[] No.45111808[source]
I guess at least they're consistent (or maybe herd mentality) since both azure-cli and gcloud are both in python, too
5. mdaniel ◴[] No.45111861{3}[source]
I believe they're discussing that awscli was targeting Python 2.x for the longest time, e.g. https://github.com/aws/aws-cli/blob/0.4.1/setup.py#L48 up through https://github.com/aws/aws-cli/blob/1.19.112/setup.py#L64 from 4 years ago, seemingly cutting over to Py3-only starting with https://github.com/aws/aws-cli/blob/1.20.0/setup.py#L62

I didn't go digging into it, but I'd guess they used the ubiquitous "six" library for backporting unicode functionality, but the point is likely "but why start underwater?!"

6. mdaniel ◴[] No.45111873[source]
but, hey, at least they get to be ultimately dynamic, leading to horeshit like this https://github.com/aws/aws-cli/blob/2.28.22/awscli/botocore/...

What does `create_client` return?! don't you worry your pretty head about it, it'll be whatever you want it to be! flexability!!11