That isn't a "new" model with all of the uncertainty that goes along with it though. Rav4 and CR-V have established reputations, entrenched supply chains, etc... A better comparison would be brand new models, not refreshed old models.
I guess that is fair, but according to this carsalesbase.com site, it isn't even remotely close. Tesla has built/sold more Model 3s in its first year of production than anything else I can find...by a lot. They built/sold more in the past few months than entire years for all of the other models I have checked.
That's why I asked what models the other person looked at because so far all of the information I can see from the site that they linked confirms the "pro-Tesla" person's statements.
Which models did you look at? I don't remember a lot of models that are new to the market recently. I checked the Mazda CX-3 and the Nissan Leaf, and the Model 3 does appear to have crushed both of those based on first year numbers.
Obviously we don't know yet, but I would be absolutely shocked if they don't basically flag everything about well-known politicians as "political", and paying to boost something like that should fall under the new restrictions. It would be trivial for most large tech companies to make an automatic "political post" classifier at this point. The post "boosting" use case is a pretty easy target too because blocking someone from paying to boost something is fairly low-risk.
"Zero cost abstraction" is like a sarcastic joke at this point in web development. If you pull up performance comparisons for web backends, a lot of the popular ones based on interpreted languages are absolutely abysmal when compared to c++ or Java code (Node is a good example). Many definitely have streamlined development workflows and have nice, high-level abstractions, but at a cost to performance. I don't mean that Node is useless or something, sometimes it makes sense, but it still forces you to compromise.
Front-end frameworks are even worse. A lot of older (but not "ancient") PCs are unusable on the modern web because of poorly-optimized JS or Adobe Flash (a decent portion of this issue is also due to the inherent inefficiency of JS and Flash as well). Fortunately, Google has been making strides with V8, Mozilla did awesome with Firefox "Quantum" and everyone is slowly ditching Flash, but performance still seems to be an ever-present issue.
I have thought for awhile, and continue to think, that developers avoid "premature" optimization too fiercely. Yes, there are diminishing returns with optimization effort, but too often people interpret "avoid premature optimization" as "never optimize unless it feels slow, and even then only if it feels slow when it's the only thing running. Otherwise, blame everything else that is running first!"
This is a really good point, I hadn't thought of this before. Because of how many other options there are, the "scarcity" of Bitcoin is only real if there is something that is going to prevent other cryptocurrencies from being used, or promote Bitcoin above all others. Given that Bitcoin has been demonstrated to be inferior at scale vs. some of the other options, I don't see a reason to expect that it will continue to be the most prolific in the long term. By extension, there doesn't seem to be an obvious indication that any of them will see a lot of use in the long term.
To piggy back on something you said: a big issue I noticed recently is that it seems a lot of the websites people use to track this stuff have charts in <other coin> vs. BTC rather than <other coin> vs. USD (or some other established currency). As BTC goes up and down, these charts are extremely misleading due to the volatility. This dramatically pushes things into fantasy speculation land since people are valuating their speculative investments based on another very speculative investment. If BTC drops in USD price, and your altcoin of choice gains slightly vs BTC, these charts would show a "gain" when I think in reality it is still a loss.
within roughly 5 years or so (very rough guess on my part), all of the available Bitcoin will have been mined. At that point, the mining part of the equation will be moot, leaving only the blockchain infrastructure to consider. Note that this may not hold true for various "forks" of the bitcoin blockchain, or for other cryptocurrencies.
The Java performance was the most interesting part of the results for me. I'm glad it got some attention. I have been developing the opinion for awhile that, as an industry, we've become far too avoidant of "pre-mature" optimization. It is astonishing to me how much slower a lot of this stuff is than Java.
Granted, I also think considering Java to be "not compiled" is a slight misrepresentation since it does get compiled to Java bytecode.
This is a fair point, but most vocational programs last years not months, so that is where the analogy breaks down here. I think "vocational" code schools offering 2-year degrees would be very, very attractive as an alternative to a traditional CS degree (both for students and hiring managers), but that's not what we're looking at.
According to a quick Google search, the average program length for these boot camps in 2015 was 11 weeks. That is on par with a single semester at a university. Even if you take a heavy course load of only practical CS courses, one semester is not nearly enough to prepare someone fully for a full-time dev position at top-tier companies. Sure, they may be able to answer the interview questions...but then what? I'm pretty skeptical of this trend and don't see it ending well for most of the boot camp graduates or companies who hire a large number of them.
Also to be fair, learning how to select elements by CSS class is so trivial that it doesn't effectively separate levels of developers. Whether you choose the basic JavaScript version or one from a popular framework, it should take less than a minute to look up if you don't already know it. I imagine that seasoned developers (and possibly recent CS grads, depending on school) are much, much less likely to waste time wondering why $(".myClass") is giving them a "$ is undefined" error in their Angular/React/etc... project.
I might be wrong, I don't have any direct experience with boot camps, but stripping dev skills down to just the minimal, core, practical skills needed to build a working prototype in the language-of-the-month seems like just the latest version of the same short-sightedness that has been plaguing businesses for years. Low-risk, long-term success will always come from building on experience, not "hacks" and short cuts. There will be exceptions/outliers, but they're just lucky, not a model to be copied.
This is exactly what I was thinking. Put into words that are easier on my brain: If the things taxes are being spent on (social programs, shared services, and shared spaces like parks) are significantly better, one might still have a "better living" with a lower salary.
One of the main aspects of this that is very relevant to Americans is how easy or difficult it is to be fired and what programs are available for those who lose their job. Even if you are never fired, simply the threat of it can cause anxiety and stress that simply wouldn't exist in places where it is harder to be fired and which have better programs for people who are fired.
I imagine that if the service call to verify mock data fails, it should retroactively invalidate all tests based on that mock data, or at least this should be understood to be the case by the people reviewing test reports.
I have been cringing every time I see/hear the word "disrupt" (in its various forms) for a couple years now. In pretty much all cases, the more often a given person uses that word, the more vapid I come to think they are.
"Except digital signing makes the compromised OS totally and utterly useless for other phones."
This carries with it the assumption that the digital signing and verification mechanisms are infallible and impervious to attack. That is an unwise assumption. Even if a software system appears to be perfectly secure at a given time, it is reasonable to assume that at some point a vulnerability will be discovered.