I wonder if they do bin them though, just not for iPhones or iPads. Perhaps today's A13/A14s that have small defects are tomorrow's Apple TV or HomePod CPUs.
I drive a 2013 FRS (older US version of the 86) and I'll experience weird dropouts all day like once every couple of months. Otherwise it works flawlessly. Very strange. You might try using it now and again and see if the problem "just goes away". Very frustrating though. I did not opt for the touchscreen however. I think my head unit is made by Pioneer.
There's a fascinating write-up by John Carmack in there about porting the original Wolfenstein 3D to the iPhone. Crazy to think that was over 10 years ago.
Thanks for taking the time to type this up. Having just written a class similar to Span in C++ I was curious as to how this would be accomplished in C#.
I'd say for strings it's entirely domain dependent. Many problem domain's won't ever use `std::variant` but may require that all strings live in ROM, so for those domains the default behavior makes perfect sense. If you want to compare C++ to modern languages, I get it, it's obtuse, but C++ is also used in instances where other languages can't be and so has to at least support doing things that may be unintuitive in other domains. That being said it would be nice if we could deprecate things with wholly better replacements like raw pointers, raw arrays, etc.
That's his reference book. It's not designed for systematic learning. It's designed as a reference, as in "cut-and-paste stuff". You want one of his other books, meant to take you from zero to literate in not just C++11 but programming in general: https://www.amazon.com/Programming-Principles-Practice-Using...
This. So much. Declaring intent (what) is much more useful than declaring the mechanics (how). I don't typically care about the "how", just the "what". And the more readable that is, the better.
I'm pretty sure the mobile CPUs support at least 64GB of DDR3. So the memory subsystem would be desktop class but they could use the same mobile CPUs. Seems to me that might have been an option if they didn't also shrink the battery.
I think the lack of any news on other products accounts for at least 50% of the backlash. As Apple's product line stands the only products looking forward to a USB/TB3 future are laptops. Evaluated in this vacuum, the new MacBook Pro doesn't deliver. If they had showed us new iMacs and and updated Mac Pro there would be more options and more insight into what Apple's vision of that future looks like.
That's quite the blanket statement. Refactoring is just as much of a problem in statically typechecked languages. I write unit tests for a large C++ codebase and find them incredibly valuable when refactoring. Typically each class has a responsibility. The unit tests verify they are carrying out that responsibility correctly. Acceptance tests validate behavior across multiple units (the hard stuff). I fail to see how unit testing in languages like C++ wastes time. We spend far less time finding and fixing bugs than when we didn't have them.
I don't think it's a given that breaking it down introduces complexity. I've found that creating a sub-function for the sole purpose of just giving it a name does wonders for making it easier to understand the code. Names describe intent and are easier to remember than lines of code by themselves.
Which shell are you using? With fish I find that it's history is somewhat context sensitive based on the present directory. Because of this I've found myself less frustrated when working with the history across multiple tabs.
Have you ever used OS X? Application state can be preserved and restored across reboots. Most apps do this automatically. Actually I haven't encountered one that doesn't.