kakes

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

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.

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

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.

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.

In case anyone is curious - as I was - here's the commercial: https://youtu.be/uTVlnehpRHQ

(Not the Toys R Us channel, in case you don't want to give them direct views.)

Sounds like the kind of thing a paranoid schizophrenic would lose their mind over.

I feel like everyone has their preferred builds they kind of gravitate to and feel comfortable with. That, and for me, a lot of luck to make up for my lack of skill lol.