The problem is not encoding the result.
The problem is that you need some support from the language to make it easy to deal with. Otherwise you’ll get into go-style infinite if (err != null) handlers that will make your code unreadable.
It has Evil if that’s your thing :)
I dislike that it takes way too long to boot, but IMO the defaults are just fine.
In C++, ignoring anything that any other language provides…
I mean, yeah, if your language does not support error values, do not use them.
That’s a valid point.
There are two kinds of good serialization languages, the ones where values are black boxes and only serialize the data structure, and the ones where everything is completely determined and can be turned directly into an API.
JSON is neither, but it’s closer to the first than YAML. XML is the first, while the SOAP standard almost turns it into the second. TOML is about as close to the first as JSON.
TFB, the numbers are not defined as 64 bits floats.
They are just not defined. At all.
The end of line also has semantic meaning. Both indentation and eol are whitespace.
Haskell supports both semantic whitespace and explicit delimiters, and somehow almost everybody that uses the language disagrees with you.
But anyway, for all the problems of YAML, this one isn’t even relevant enough to point out. Even if you agree it’s a problem. (And I agree that the YAML semantic whitespace is horrible.) If YAML was a much better language, it would be worth arguing whether semantic whitespace breaks it or not.
Anything that didn’t need that kind of security from the beginning also wouldn’t break if it’s built.
The stuff that would break are all vulnerable because it doesn’t exist.
Have a code, where you can really describe the error; try to use the correct HTTP status (your example doesn’t); don’t ever use status 200 for errors; and finally, have an “error” key set to something somewhere (I’d write the error code to it).
The message is optional.
So, the simplest version would be:
HTTP/1.1 401 POST /endpoint
{
"error": "UNAUTHORIZED"
}
Yes. Actually implementing Scrum can go either way, but going out of your way to learn and apply it is certainly going to end in tragedy.
The OP wants the paginated table data and the count. With a single query execution.
And bribing governments…
Everybody would use Mercurial, since Fossil completely lost the race, and both Subversion and CVS are unfit for today’s needs.
What is too bad, because Fossil would be much more productive than Git or Mercurial if the software just finished running at all; and Mercurial is way easier to learn than Git.
And those are only fully packaged user-facing software.
I’d guess almost all of the Rust code for low level hardware access is maintained by a single person. Most of them once joined forces and created a standard, it had 4 developers last time I checked. The only usable cryptography library for C# has a single developer, and while on crypto, that meme got widespread because of OpenSSL, that had a single developer who spent most of his time on OpenSSH and other BSD user-facing software.
Also, while we are on crypto, the modern algorithms were all created by a single researcher, that got famous for a work on how to decide if you can trust a crypto algorithm. Almost everybody uses his code.
Anyway, that meme first appeared because of Javascript, when a developer removed his library (with ~10 lines of code) from the language’s repository and almost every Javascript software broke.
Using AI in the marketing is a sign you don’t have much else to show for.
To me it’s a sign that you have spyware included, will depend on a perfect network infrastructure, and will stop working in 2 years.
But my guess is that for most people it’s a sign the product is made by some psychopath-like company like Facebook.
It’s a ton of stuff because M$ keeps slapping the branding on everything they can, regardless of how relevant it is.
Every time something from MS becomes famous in a good or neutral way, they do that to dilute the brand.
There’s a reason they do that: Files can get big
Oh, boy. Wouldn’t it be great if servers had a way to discover the size of the files on their storage without having to read them?
adding various code highlighting and interactivity costs performance
Somebody, quick, there’s work to be done on language theory so that we learn how to do those things with a cost just proportional to the file size!
(No way! Who is that Chomsky guy you keep telling me about?)
Did you hear about it when that same software had that same problem on its Linux endpoint system a couple of months ago?
Well, me neither. I can’t tell how much of if is “anybody willing to use something like that will also want a Windows server” (crazy people), or “nobody that wants Linux would accept it”. Those two are not exactly the same, and I don’t know how well the auditors that keep pushing this kind of shit into companies interact with the culture.
You mean like NixOS?
It wouldn’t technically stop anything, it would just make your live Hell on Earth if you tried to add that self-updating ring-0 proprietary software in your servers.
But I guess what you are looking for is immutable infrastructure? That one would stop the problem.
TBF, I don’t even remember why I stopped using the daemon. But it’s currently 3 seconds, so I dislike it… but not so much that I’d prioritize solving the problem versus complaining about it on the internet…
Anyway, I’m adding the server into my DE’s startup. Thanks for the reminder.