Honestly, where do people live that the DMV (or equivalent - in some states it is split or otherwise named) is a pain? Every time I've ever been it has been "show up, take a number, wait 5 minutes, get served" - and that's assuming website self-service doesn't suffice.
ripgrep is one of the main reasons I got interested in rust. it worked so well, it piqued my interest that it was written in rust. many years later, very glad about that. been using `rg` daily since then as well!
I haven’t used qbasic in years, but hacking on nibbles is why I learnt qbasic, and I’d say that experience is a decent early chunk of why I’m an AI professor now. Nothing wrong with playing with languages that feature software you love!
imagine some people started using hammers as weapons, leading to some gruesome murders vividly depicted by the news. as a result, construction companies started advertising that this house was built without the use of ANY hammers. that's how I feel about cookies.
cookies are not the problem. spyware is the problem. the way cookies work is, the server includes a "SET-COOKIE" header in its response. it is literally a request, which has no power, other than your computer deciding to store the data locally and include the cookie as a header in its subsequent requests.
somehow instead of us collectively relying on our own user agents to not comply with requests from remote servers that are not in our interest, we settled on deciding the cookie itself is a dangerous mechanism, which is stupid.
was expecting to see examples of python tests you would use, presumably for testing the rust code? like, how would writing the tests in python be easier?
needed to send "raw" http requests instead of using their bloated sdk for reasons, and requests failed with "content-type: application/json" header, but succeeded with "content-type: application/x-amz-json-1.0". get out of here with that nonsense.
I feel this way about pretty much every aspect of AWS I have touched in my career. Overly bloated, overly complex or weird home brew implementation for no clear gain.
Didn't you know, Amazon owns JSON? They acquired it this week, please update all your Content-Type headers within 12 months otherwise you will be in violation of their IP holdings.
If they use a non-standard version of JSON (for example, one supporting comments, or one with rules about duplicate keys, or any other rule that's not part of the underspecified JSON spec) they should use a custom content type. Something can be valid JSON but invalid AmazJSON and this is exactly how you would distinguish between the two.
that's honestly a leak of internal details lol. (leaky abstractions)
because internally most apps are using the coral framework, which is kind of old, using this json format as it has a well defined shape for inputs, outputs, and errors.