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.
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.
It would be much better if it stopped missing the version of the code you are working on and locking while starting multithreaded code.
People only discovered that multi-layer non-linear neural networks work at the 90s. It’s not really reasonable to equate perceptrons with the stuff people use today.
When you enter an apostrophe, and the site returns a 500 response stating you are trying to attack it. (And yeah, it’s always 500, not 400.)
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"
}
But i still think C++ has more footguns than Prolog.
They are different kinds of footguns. The C++ ones keep security, ops, management, suppliers, customers, and the public up at night; the prolog ones keep you up at night.
I have been wondering that lately…
Hum… I’m not sure I wouldn’t make that same mistake.
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.
Odds are that your computer doesn’t export any language where it will do exactly as you say (amd64 machine code certainly won’t execute exactly as written). And how much difference it makes varies from one language to another.
But the specific example from the OP, of uninitialized variables, is one of those cases where the C spec famously goes completely out of line and says your code can do whatever, run with a random value, fail, initialize it, format your hard drive, make a transaction on your bank account… whatever.
None of that is “Python”. You want to learn a language and automatically know everything there is to know using Math?