tyree732

https://en.wikipedia.org/wiki/Sagittarius_A*

Put another way, Google may have just notified the world of black-hat hackers of an issue they weren't otherwise aware of, an issue that demonstrably will not be patched for some time. If that is the case, then Google just recklessly endangered people's computers in the interest of raising awareness of Microsoft's poor turn around time on these issues. There is also the very real chance that this issue was already known by the black-hat community, in which case there isn't nearly as much lost by reporting here, but that's a gamble Google is making in order to make a point.

"And of course, feel free to pop open a delicious Pepsi as you listen to this next act, Act One. By the way, we are not getting paid for that at all."

I'm guessing it just happened to be the best available audio interview with William Cimillo.

With Mozilla, the supply is one item, the default search engine for the search bar, something which has high demand. That means if Google were to become less interested in paying for the search bar, Bing would be waiting at the gates to do so. They could lose money if that were to happen, given that Google was the highest bidder, but that in no way makes them beholden to Google.

One day I checked my account and discovered that I had accrued a number of overdraft fees. Apparently sometimes merchants (namely gas stations) will put a temporary charge of a dollar against your credit card, then later correct the charge to the correct price. This caused my account to overdraft as HSBC didn't deny the correction, then with my account overdrafted as of the date in question, all subsequent valid charges I had done against the account assuming a one dollar gas charge were made as overdraft charges. Contacting customer service and reminding them that I had in fact disabled overdraft was not enough to convince them of anything other than giving me a one-time partial credit of fees, so I switched banks.

I don't know if that is still how things are done over at HSBC, but ultimately the point is that disabling overdrafting is not some panacea for the problem, as ultimately there are situations that can still get you in trouble.

You also believe that the power dynamics of an interview are different than the power dynamics of a company, as in an interview making a mistake can mean the difference between being hired and not. I don't disagree with you here, as ultimately making a mistake in an asymmetric negotiation at a company won't always get you fired. In this case, what I was providing a response to my parent comment, that if asymmetric negotiations are a problem for a person then a company will never work for them. These two things are not exactly the same, though I wouldn't fault someone for taking difficulty handling one to imply difficulty handling the other.

Or, saying it another way, as a software engineer, you are paid well enough to easily afford your vacation days unpaid. Having paid vacation days for yourself when so many people in the world don't comes across as completely unfair. Would you be willing to work with such a person?

Besides, anything the C++ standard template library map does when implementing a red-black tree is exactly what you would need to do if you wrote your own, minus having things like allocators (which are incredibly useful for those that need them). You speak of overhead due to "objects, classes and implicit memory management". Inevitably, any implementation of a data structure of substance in C ends up looking like c++-ified C. Want to create your hashtable? Call hashtable_init and get back a hashtable_t. Want to insert into it? Pass your hashtable_t, a key and a value into hashtable_insert. Even worse, you either have the choice of making all of your data void* in the data structure and casting into and out of your interface or making awful macros to define the various methods and structures for the types you would like to use. It's like you're stubbornly writing C++ in C.