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.
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 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.
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.
Love how they make this sound like some incredible feat. When you aren’t bound to license agreements, turns out it’s actually very easy to have a “massive” content library. Literally the only hurdle is storage space.
You absolutely aren’t wrong there.
Always in favour of healthy competition.
Those sneaky bastards.
Haha well that’s uhh…
Ngl that’s a interesting idea. Would definitely want it running locally, though.
80s Goon Cave.
The thing is, I kinda get it in a way. Like, having an account lets them offer so many more useful features, and over time they might just see it as not worth supporting two “types” of users, so they lean more on requiring an account.
Obviously, a lot of this is driven by execs trying to make their line go up, but even without that it does make sense to a point. Not that I agree with it at all, but I see how it would happen.
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.