> IMHO GCC's special handling of memset() is broken
I appreciate how you've distinguished your opinion from objective facts. E.g. according to spec, it's not broken, but it's a perfectly valid opinion to hold that the spec is broken too. :-)
I think the most amusing case of UTF-16 considered harmful would possibly be the choice, in WPF/Xaml, to use UTF-16 code point offsets to reference positions in XML strings -- while supporting UTF-8 XML encoding. It can create the situation where, even if the input and output are both UTF-8, you'll nonetheless need to transcode into then out of UTF-16 in order to perform the proper string splitting.
What has me confused is how these automated take downs, without automated appeals, don't constitute fraud. I can't go down to the local county courthouse, spamming it with grossly erroneous and frivolous claims documents, and expect to just walk away. There are laws against that sort of thing.
Yup, I've seen this as well, way too often. Rather than a function, you get a class, rather than arguments you get constructor parameters, and then the get stuck at what to name the method that actually does anything.
Yeah, there's also "an excellent opportunity arose," and "time for a new challenge," or "looking for a bigger/smaller, riskier/stable team/company/toaster/product.
Ditto. Also, from previous managers they may have learned that criticism, even constructive criticism, is a great way to bag a negative performance review. Such effects need to be accounted for.
Not really; it's clear from Asimov's story that the question is about a closed system. The abstract for the paper you cited implies the led was externally heated, acting as a thermo-couple. The closed-system efficiency was still <100%.
As others have already pointed out, you don't need to compile from Latex on the device. The formats already have support for passable typography. Publishers aren't making an effort to use it.
Yeah, the publishers are mourning the loss of "hardcover edition" in the ebook format. That's where they make their mint.
I'm hoping that they will try (and catch on) a ebook+hardcover release model. After all, people buy hardcover either (a) because they need the product now and can't wait for paperback (or there isn't one), or (b) because they also want to show it off in their personal library. The ebook+paperback could offer that experience. Hardcover $30, Hardcover+ebook $33. That's $3 for free. Oh, hmm, looks like O'Reilly is already is doing this bit :-)
A month after each new release, you make paperback and ebook available simultaneously, offering the ebook at minus publishing and shipping costs. ($5 paperback, $3 ebook?)
The paperback managed to put the hyphen in the right place. At least it's making an effort. When was the last time you saw paperback had an out of place hyphen just because that's where the hardcover placed it?
This is especially true when "iSomething" is free. A lot of folks will want to 'buy in' to the software, out of guilt or gratitude, so will pay for "iSomething+" even if the delta is trivial.
This! We started baby sign and could communicate these basics with our daughter before she was a year old. It might not sound like much to start communicating 6 months earlier, but I can only describe it thusly: awesome.
I appreciate how you've distinguished your opinion from objective facts. E.g. according to spec, it's not broken, but it's a perfectly valid opinion to hold that the spec is broken too. :-)