It's partially because of the lack of competition and partially because the process technology itself has slowed down. We're starting to run up against the limits of silicon, going from 22nm to 14nm isn't as big of a performance increase as going from, say, 90nm to 45nm was a decade ago.
The -E line of processors is always one process generation behind the mainstream chips, these are processors with more cores/PCI lanes/cache on an "enthusiast" platform. Essentially unlocked Xeons.
Sure I do. So, likely, do you and most other people reading it, or at least have a general idea. So what's the point of typing out my specs? Should I also type out the specs of my Nexus 6P or just tell you I have a Nexus 6P?
It would help inform your discussion of the article if you read the first paragraph. A) This is VS Code, not Visual Studio, B) This is a third party open source plugin
There is a wide gulf of difference between installing an IDE from a trusted corporate entity who would be sued if they did this kind of thing by default without warning vs. installing a 3rd party open source plugin from a developer you've never heard of without reading the description.
but if you're a docs user wouldn't you expect docs to look and feel the same everywhere? That's the choice google has to make. Do we worry about our app matching YOUR OS's design patterns, or do we keep our applications consistent across all platforms?
but if you're a google docs user isn't it safe to assume you probably use it on more than one device, and google docs looking and working the same across devices is more important than the individual docs iOS app looking like all your other iOS apps?
Material Design isn't just about Android Apps though. They make libraries for websites too, and have guidelines for all types of devices built into the spec. Google isn't using MD in their iOS apps to bring Android design to iOS they're using MD in their iOS apps because they believe MD should be a universal design paradigm for applications and web apps. You can argue that it shouldn't be, you can not like it as a design framework in general, but it's not about Android vs iOS it's about Google's vision of application design regardless of platform.
Look at the scales on that chart. It starts at millions of years before present, then drops to thousands of years before present, and then our last 200 years is basically a vertical line at the very end of the graph.
depends on what's in the prenup and who is making what. Maybe the prenup says they spit everything 50-50 and Susan makes more/has a nicer house. Or maybe she's going in to a more lucrative career field. Or, maybe she's just offended at the notion that her future husband is already planning an exit strategy (that last part is mostly my own feelings about prenups coming through)
Yup, a preorder without the legal restrictions that come with preordering (in some US states you can't charge a credit card before the order ships). So this way they can use the money from their "preorders" to actually manufacturer the product that is being shipped, where traditional preorders are more about gauging market demand and possible using that as leverage to acquire funding to go to manufacturing.
Setting up an email server that won't get blacklisted by the major providers within a week of you setting up is difficult, time consuming, and often expensive.
probably leaving the "corporate dicks" part off would have been enough. Maybe the don't fork over the $30k but they'd probably have made an offer at least. Calling them "a bunch of corporate dicks" at the end makes it clear you're just throwing out what you think is a high enough number to tell them to fuck off.
I'm actually largely experiencing this issue right now trying to pick a front end framework for an FOSS project. I know I'm using Rails on the backend because that's what I'm most comfortable in, but I can't decide between Angular.js and EmberJS and 99% of the articles comparing the two just sound attack-ey and biased and I don't want to make a decision based on someone else's preconceived biases. If anybody knows a good compare/contrast between Angular and Ember for use with Rails that is, mostly, unbiased and doesn't resort to "this framework is better because holy shit did you see how the other one solved this same problem in a slightly different but horrifically terrible way?" I would greatly appreciate it.
Knowledge nurses talent, but it is not in and of itself knowledge. The knowledge of how to solve a problem that has been solved before is incredibly useful, but the real talent in our industry is the talent to solve new problems in new ways, and most people develop that talent but not just looking at how a problem was solved but deconstructing the process of how the designer of that solution came to the conclusion they did.