I guess what I’m saying is that I think things will generally stay balanced the way they are. Monoliths are never going to completely die out, and neither are microservices.

They both serve different functions, so there’s no reason to think one will “win” over the other.

I mean, if anything, I would say microservices are the present.

As assaultpotato said, horses for courses, but I mean, microservices aren’t really a new concept at this point.

It’s called the linguini effect.

Speaking of analog: Light Guns don’t work on modern televisions due to the high latency relative to CRT screens (which had essentially zero latency).

It baffles me that they sell Chrome as private and/or secure, and baffles me even more that people believe them.

“Turing Completeness” != “Turing Test”

I assume this is a joke?

I had it running on Windows (no container) a while back. Wasn’t particularly difficult at that time, at least.

Can’t give any advice here though, since all we’ve been given to work with is an OS.

take up subsistence farming

Where?

Can’t say we as a species have a great history of granting rights to others.

Heck, now I want pizza…

And not only that, but if you spritz leftover pizza with a bit of water before putting it in the microwave, it brings out the flavour more and prevents it from drying out.

(Figure that’s about as relevant.)

Those are two very fair points - I agree.

I’m not sure I understand what you mean.

For an API there should always be a version parameter/endpoint, imho.

Edit for further context: Ideally, a parameter.

You’re in luck! The book I’ve generally heard recommended to beginners for Python is available for free online!

The biggest reason for me is that it’s less data to send over a network. Especially when I’m working with lists of objects, including null fields can add a noticeable chunk to the payload.

There are some cases where it might be worth it to differentiate “No value” and “No attribute”, but in most cases they can be treated the same, since the data should really be validated against a schema anyway.

Yeah, I’m also confused. If an attribute is null, I would prefer to simply not serialize it.

I’m sure there are edge cases where someone might prefer to include null attributes, but generally they should be treated the same either way.

I say we ditch this nonsense altogether and go back to vague descriptions of the Sun’s position in the sky.

That used to be the case, back when Steam Sales were a chaotic feeding frenzy of discounts. These days it’s pretty much the same throughout.