foxtr0t

>Then why comment?

Because the instruction list from above isn't backed with any solid reasoning and because commenting is what people do on HN.

>You clearly don't understand the use-case that AWS fits.

Pray tell, what is this enviable use case that I so clearly do not grasp?

So, to summarize, you should:

1. not use the programming language that works best for your problem, but the programming language that works best with your orchestration system

2. lock yourself into managed services wherever possible

3. choose your api design style based on your orchestration system instead of your application.

4. Use a specific frontend rpc library because why not.

...

I've hacked a few lambdas together but never dug deep, so I have very little experience, but these points seem somewhat ridiculous.

Maybe I'm behind the times but I always thought these sort of decisions should be made based on your use case.

EDIT: line breaks.

That is only true if you assume the housing market under rent control is otherwise efficient. In reality it is painfully inefficient. Scarcity due to rent control (due to existing tenants holding on to leases) allows landlords to price gouge on everything from open units to parking to laundry.

If you play that dynamic forward you end up in a situation where everyone is overpaying compared to a more fluid market, even those longer term tenants.