motorest

34 ms·

601.
by motorest 1y ago
> That is used everywhere - take a look at any random API and there is roughly 90% chance that this is the authentication mechanism used. I have no idea where you got that idea from. I'm yet to work in a project where any service do
602.
by motorest 1y ago
> JSON doesn’t really have data types beyond very simple ones What do you think primitive types are supposed to be?
603.
by motorest 1y ago
> Well the competition is REST which doesn’t have a schema or required fields, so not much of a problem. A vague architecture style is not competition to a concrete framework. At best, you're claiming that the competition to gRPC is
604.
by motorest 1y ago
> Care to list them? From the top of my head, OData. https://www.odata.org/
605.
by motorest 1y ago
> REST is just too "floppy", there are too many ways to do things. I think there is some degree of confusion in your reply. You're trying to compare a framework with an architecture style. It's like comparing, say, OD
606.
by motorest 1y ago
> I've seen some systems with a lot of pieces where teams have attempted to avoid repetition and arranged to use a single source of schema truth to generate various other parts automatically, and it was generally more brittle and ha
607.
by motorest 1y ago
> (...) and part of the reason for this is just that defining media types is not something people do (...) People do not define media types because it's useless and serves no purpose. They define endpoints that return specific resou
608.
by motorest 1y ago
> We should probably stop calling the thing that we call REST (...) That solves no problem at all. We have Richardson maturity model that provides a crisp definition, and it's ignored. We have the concept of RESTful, which is also i
609.
by motorest 1y ago
Don't stress it. It happens to the best of us.
610.
by motorest 1y ago
> Nowhere is JSON in the name of REpresentational State Transfer. If you read the message you're replying to, you'll notice you are commenting on the idea of coining the concept of HTTP/JSON API as a better fitting name.
611.
by motorest 1y ago
> So the lack of "HATEOaS" hasn't even been noticable for me. I think HATEOAS tackles problems such as API versioning, service discovery, and state management in thin clients. API versioning is trivial to manage with sound
612.
by motorest 1y ago
> HTTP/JSON API works too, but you can assume it's what they mean by REST. This is the kind of slippery slope where pedantic nitpickers thrive. The start to complain that if you accept any media type other than JSON then it&#x2
613.
by motorest 1y ago
> I sympathize with the pedantry here and found Fielding's paper to be interesting, but this is a lost battle. Why do people feel compelled to even consider it to be a battle? As I see it, the REST concept is useful, but the HATEOAS
614.
by motorest 1y ago
I think OData isn't used, and that's a proper standard and a lower bar to clear. HATEOAS isn't even benefiting from a popular standard, which is both a cause and a result.
615.
by motorest 1y ago
> It’s the worst kind of pedantry. Simultaneously arrogant, uncharitable and privileged. I'd go as far as to claim it is by far the dumbest kind, because it has no value, serves no purpose, and solves no problem. It's just triv
616.
by motorest 1y ago
> On the other hand, if you tell me that something is a "REST API", I already have a very good idea about how to use it (...) Precisely this. The value of words is that they help communicate concepts. REST API or even RESTful A
617.
by motorest 1y ago
You're being needlessly pedantic, and it seems the only purpose to this pedantry is finding a pretext to accuse everyone of being mediocre.
618.
by motorest 1y ago
Housing and urban planning. It's the single most important factor in quality of life, and the root cause of so many critical issues such as energy usage, pollution, climate change, and even geopolitics.
619.
by motorest 1y ago
> So you didn't think they were dismissive or trivialised the issue? What issue would that be? People falsely claiming they suffer from conditions they do not have? Or is it when they claim they struggle with a condition they self-d
620.
by motorest 1y ago
> Did you even search for anything before making that idiotic comment? You acknowledged the fact that "there are those who self-diagnose without really suffering from a condition". I, in turn, added to the fact that you pointed
621.
Portland Pattern Repository(c2.com)
2 points by motorest 1y ago|0 comments
622.
by motorest 1y ago
I don't think this blog post was researched well. It reads like a parody, in fact. It starts with a project, throws a bunch of assertions and ill founded opinions, proceeds to present a series of pessimizations, and somehow concludes t
623.
Azure Architecture Center(learn.microsoft.com)
2 points by motorest 1y ago|0 comments
624.
by motorest 1y ago
> Benchmarks? I hope you mean detailed writeups on robustness, because performance is not a consideration yet. I don't think there is ambiguity. Either you have some way to objectively corroborate your personal claims, or you don&#x
625.
by motorest 1y ago
> The top-level comment seems to attribute all such people who identify with those symptoms as doing so because of a trend. I think the only source of disagreement is in the way you chose to frame it in absolutes, i.e., "all such pe
626.
by motorest 1y ago
> Im sure there are those who self-diagnose without really suffering from a condition, but you do realise time blindness is a real issue, right? So is Munchausen syndrome, but somehow people don't self diagnose that one. https:&#x2
627.
by motorest 1y ago
> Experimental has no defined meaning with respect to the release process. Nonsense. And to make matters worse, you're commenting as if trying to sneak features in bug fixes late on the release process has no impact on quality assur
628.
by motorest 1y ago
> My point is that there are people low on the agreeableness scale, and they can often be exceptional engineers. Not true. Every single egregious asshole who is unable or unwilling to work in a team environment is quite bluntly incompete
629.
by motorest 1y ago
> We have enough user reports of multi device testing that they put both bcachefs and btrfs through, where bcachefs consistently survives where btrfs does not. We have much better repair and recovery, with real defense in depth. Are any
630.
by motorest 1y ago
> You aren't doing your job as a leader if this is your attitude to good engineers. This is precisely the mistake you are making: conflating egregious types who post code as "good engineers". They are not. They are incompe

More ›