develatio

i think a very big chunk of it is still valid, despite being 15y old

Thank you so much!!

if the author of this blog reads this: can we can an RSS, please?

I cried. Then I laughed. Then I cried again. I can feel all the pain of the entire thing (don't ask me why). Amazing. Bravo!!

can you add [2018] to the title, please?

I think this is very similar to Django’s ORM.

How would Meta gain access to my home if i don’t install Meta’s apps on my Vision?

and "that's it"? I mean, it does sound like it might introduce unexpected UI behaviour, but are there any other more serious / dangerous consequences?

I was not able to understand why these code points are bad. The post states that they are bad, but why? Any examples? Any actual situations and PoC that might help me understand how will that break "my code"?

I’m gonna go ahead and flag this one. This rant doesn’t make any sense (as other people in the comments are pointing out)

True. Most services (unless your service is a demo/toy project, as I stated earlier) have way more traffic. It might not be evenly distributed though the day, but if you add all the CPU time in a day, I’m sure it will exceed 24h. So that leaves me with the question for who is this? Developers that are starting and want to deploy something small?

Say I want to deploy a service that is currently receiving 1rps at a constant rate, no upticks, no gaps. Wouldn’t that be the cost? If the answer is “yes”, then no, that is a terrible pricing.

If my math is not wrong, running a single “standard” container during 1 month (non-stop) would cost ~55$.

This looks extremely expensive for anything other than a simple demo/toy project. I can’t think of a reason I’d use this for heavy services instead of using [anything else]. Maybe I’m not seeing the use-case?

How does networking between several “services” (containers) work?