I dunno, but there are still plenty of lactose intolerant people that insist on drinking milk and not taking any medicine...
So, I'd guess a bit of both.
I'll just also add that getting sick because of the milk doesn't alleviate any starvation.
I dunno, but there are still plenty of lactose intolerant people that insist on drinking milk and not taking any medicine...
So, I'd guess a bit of both.
I'll just also add that getting sick because of the milk doesn't alleviate any starvation.
Hum... So, condensed matter physics should be standard at an EE curriculum? With the necessary quantum mechanics requirement too? Some discrete topology would help, so I guess we should add that too, after the continuous as a requirement, of course.
Solo shoots, Kirk punches.
An electrical engineering course usually won't teach you how semiconductors work, so those other species should look on the mirror before criticizing.
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"
}
That "captive" word is quite plain. You are the one overlooking it, this is not your normal corporate-speak.
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.
Ouch.
I've once decided that "hey, software interaction is logic, so prolog should be the best for complex protocols and UIs!"
Quite soon I understood that no, "complex protocols and UIs" are a problem all by themselves, enabling them makes them worse, and enabling them with prolog makes them even worse.
Up to this day I'm stuck trying to make data quering more "programming-like" than the restrictive thing we have with SQL. I've backtracked a few times already after noticing that I just designed prolog again.
But fear not, at some point one of us will finally find that problem domain for what prolog is really suitable. I know of an entire company betting on using it for describing access control rules, maybe they are up to something!
It's futile anyway...
It's certainly interesting and unexpected.
Well, I'm disappointed with almost every Star Wars thing... just more with the sequels.
At the same time I like most of them.
Well, if you do the math, it lasted closer to -1000 years...