upvote
> they could have polished their product and showed some love by configuring the repo details and put the website there

This feels like such a weird nit-pick when AWS is criticized for not moving quickly enough. Why should I care if there's a link in the side bar, when there's plenty of links in the `README`? If anything, I'm happy that there's alternatives to Localstack that are supported by AWS themselves that I can begin incorporating. They have a well written `README` that I can start working with and a User Guide to get me started. What else could I want?

> Did you look at the blog post as well?

I did.

> Does it look like a product that some team there loved and will care for? Or the output of some exercise for some enterprise content?

Do you even have the grounds to cast judgement like this when you admittedly didn't even look hard enough?

reply
I looked, but you're mistaking my critique here: I value polish.

This lacks polish.

Small details like getting your GH repo set up for a public audience. Lacking. Compatibility and support matrix clearly advertised? None.

If this public facing artifact exhibits a lack of care and love, what does it say about the code? I am all for vibe coding and agent software factories, but then the humans should show some love with all of that extra time saved.

reply
You might want to reconsider how you present the critique then, because that's not how your root comment came across or any of your subsequent messages, especially when engaging with (presumably) actual AWS employees in this thread replying to you.
reply
Look at AWS Copilot CLI https://aws.github.io/copilot-cli/docs/concepts/environments... and the repo https://github.com/aws/copilot-cli/.

Look at Floci (I have no affiliation) https://floci.io/ the blog https://floci.io/chronicle/ and the labs https://floci.io/labs/

Do you agree that there's a polish here that shows a team's pride in that work that is clearly missing in this work?

    > ...especially when engaging with (presumably) actual AWS employees in this thread replying to you
??? You and I are the customers. What even is this statement? Are AWS employees our benefactors? Wow. I do not care if their feelings are hurt because this "product" clearly shows a lack of polish and love.
reply
> Do you agree that there's a polish here that shows a team's pride in that work that is clearly missing in this work?

No and I think the inverse is also possible and if anything more likely. You can make a website look really pretty, really easily and have the product still suck. This is "product as a slide" in a new age where making visual eye candy with AI has never been easier.

> I do not care if their feelings are hurt because this "product" clearly shows a lack of polish and love.

The point isn't about hurting feelings. The point is about providing critque and feedback based in reality, not based on "vibes." You're trying to gatekeep people releasing software because you dont like the way they're launching it lol.

reply
This is a billion dollar company with tens of thousands of engineers. Should I feel blessed that they finally released a half assed effort?
reply
Clearly according to whom? You?
reply
If your complaint is about polish, you’re a very poor writer. It should not have taken this many replies to get that point out. But regardless of your communications skills, I disagree - this product looks fine for something released at this stage.
reply