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.
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).
Unfortunately I’m cursed with a preference for opt-out (all + block lists) post filtering rather than opt-in (subscriptions). I realize this causes issues that are entirely on me, but especially with Lemmy being so small, I like to cast as wide a net as I can.
Normally I would agree 100%. I’m specifically more harsh here just because I find the ratio to be so off.
Good question, I suppose I’m being negative about negativity.
Honestly, feel free to downvote, you have my blessing lol.
Yes.
Downvoting isn’t “negativity”, it’s a method for users to define what does and does not contribute to the content of the platform. By downvoting this content, I’m voicing my opinion that negativity is overrepresented on Lemmy, and encouraging (however slightly) more positive content to be posted.
Yeah, the doomposting is intense on Lemmy. I’ve taken up a policy of just downvoting any negative posts I see, even if I like the post otherwise, just to tamp down the negativity a bit around here.
The best and worst thing about Lemmy is how niche we are. It keeps out the “mainstream”, but unfortunately we’re easily inundated by perpetually-online doomers.
Also, I would recommend blocking users moreso than communities. Once you start looking for it, you realize that like 90% of these posts are made by just a few people/bots.
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?
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!
I also enjoy “1010! Klooni” on F-Droid.
First one coming to mind for me is Pillar Hop. Very simple, chill, and just had ads iirc (I block them, but I’m pretty sure it does, anyway.)
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.
Seems like OP is not familiar with fae mythology.
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.