There are talks internally about working towards open-sourcing it, I don't know if/when that'll happen, but it's definitely something we're interested in doing.
We didn't try any of the others, I know that there are quite a few in Golang and Java, but we're pretty python centric at the moment and felt that building it with the tools we have was a better approach.
Taking a remote job and moving to Oregon. I grew up in the mid-west and worked for a family-run real-estate business, it took a lot to leave that environment, but the housing crash of 2008 made it easier as it was a very real possibility that the company would go bankrupt.
I got a remote-job and since I could live anywhere I took the opportunity to also get away from Indiana and I haven't looked back since.
We were beginning to use React for a few things at my company, but we had our legal counsel review the license and they essentially said to use something else if we could. They weren't really worried about it, but enough so to advise avoiding it.
No, the wife beating question is completely different. It implies that you were beating your wife and at some time stopped, causing any answer given to make it sound like you're in agreement that you did beat your wife.
A negative answer to the question posed here would simply mean that you don't dislike Oculus.
I really like the idea. I often will buy books, intending to read them (someday), and then promptly forget that I have them. This would be great for that, and I like the past stats for how many pages/books I've read.
Here are some notes I took while playing with the site:
1. It would be great to have a way to add multiple books to your queue at the same time, or at least to not have to re-do your search after you've added a book. Especially when you're loading in a back-log.
2. Have more than 10 search results.
3. If you hit the back button, after a book has been added, you get the book twice. (It happened when I added Anathem to the 'will read' list.)
4. Make Author name clickable, so it shows a list of books by that author.
5. Why would I want to edit the description/title/author of a book that's already in the system? I think you might consider making this an admin function and have a way to submit changes, rather than letting users deal directly with that.
6. It would be great to have a recommendation system, or maybe more orthogonal to the system would be to specifically recommend someone's next book. I know I often have problems deciding what my next book should be.
Way to completely miss the point, Microsoft is not going to 'disappear'. Anyone who says this probably also thinks that David Copperfield actually made the Statue of Liberty disappear.
Ms Shinder must own a farm to have come up with that much straw.
The comic is already taking worst case scenario into account, that the cracker knows that your password is made of words and which dictionary you used to generate the password.
In the comic he is using a 2048 word dictionary, which gives 11 bits of entropy per word (log2(2048)), with a password made up of four words that gives a total of 44 bits of entropy.
But if we were to assume that the cracker knows nothing about our password, say other than it being all lowercase a-z, then we have an entropy per character of log2(26) or 4.7. For the phrase "correct horse battery staple", which has a length of 28, the bit entropy of that phrase, under those conditions is 4.7 * 28 = 131.6. Which is nearly to the point of the cracker being more likely to find a collision.
We didn't try any of the others, I know that there are quite a few in Golang and Java, but we're pretty python centric at the moment and felt that building it with the tools we have was a better approach.