Adventure time
Edited to clarify, my b
I think most use who use keepass instead of bitwarden do so because keepass is offline, unlike bitwarden. At least that's what I understand.
Before scraping I would verify that there is no HTTP API that you can use to craft requests instead of scraping from the website. These might be higher quality than what you can scrape. If there is no easy to use http API, go to scraping then. I would generally consider scraping the last option, unless it's a ridiculously easy website to scrape.
This is a really good point for a language that is largely advertised as being more secure due to the borrowchecker.
I heard there are quantum computing libraries in Python if that interests you!
If I were you I'd browse PyPi for any packages that look cool.
I'm not exactly sure what to think about it, but I do like how there's specific things that have their implementation in code right there. I did only look at the site for like a minute, so take that with a grain of salt.
I know it's a dumb idea but imagine how fun it would be if there was no copyright
That idea of booting from a USB is golden.
The article made a few good points, but a good amount of it was conjecture. I liked the part about comparing the two functions and showing that exceptions are faster but I think a big thing he's not getting is readability. Even in the functions he showed, you can directly see that the one using std::expected has the happy path and error path directly in the function signature, whereas the exception one doesn't.
As for the "error kind" trap he was talking about, that definitely exists, but ignores the fact that you can also get this same kind of error from exceptions. I've definitely gotten exceptions that I didn't understand from Python or Java libraries, but it's not a problem with exceptions but a problem with how they're shown. If there's nothing to tell me that I should have thought of that error, it shouldn't be an expectation for a dev to have thought of it.