* E.g. using Fastboot to flash a new firmware to an Android phone.
** E.g. using JTAG to flash a new bootloader as the device can't even go into Fastboot mode anymore.
*** E.g. my Zuk Z1.
Well, as listed on that page, it's 4k. Come on, man, I know you can read
Actually - I get a twitter page on that link.... I was slightly confused.
As for battery life, continuous integration. Tests run nearly constantly; every time I save a file, the functional test suite runs. Whenever I upload a file to one of several VMs (one for each type of server in the application cluster), another test suite runs that interacts with the site hosted on that cluster of VMs to verify that critical use-cases function correctly. The 2014 rMBP did a fine enough job keeping up, provided I didn't mind the system bogging down as the test suites ran, or artificially limiting how fast they'd run in order to avoid that (hey, we all like taking more breaks, right?) but, really, it got annoying after a time. Running that load, the rMBP could manage a couple hours of battery life, tops; seems about on par with the PC, but the PC doesn't bog down under the load. I wouldn't really say it eats batteries, considering it slightly edges out the rMBP under similar loads.
Most interesting. I run a similar suite, including DBs, webservices, etc. Granted, I at most run 2 VMs concurrently now, I ran as many as 6 previously. Still never ate this MBP battery in less than 6 hours unless I was running some hi-res or poorly coded game that kept running at 100fps or something standing still. Now that will eat battery, and make for an uncomfortable lap. The alienware machine did the same FWIW. And weighed over 10 pounds doing it.
Well, eventually they will figure it out how to make self driving cars safer than more than 99% of human drivers. When that happens, I'm not sure, but it will happen. Now, if you introduce them too early, a very risky and unsafe version of self driving cars that is maybe safer than 20% of the human driver population, but less safe than 80%, then anybody of those 80% using a self driving car would mean a safety risk.
Except that's not really how it happens, you don't need to be a race car driver to be a good street driver. A good street driver is merely consistent, appropriate speed, paying attention, obeying the traffic rules. It's not a skill level, it's a fail rate. You do things right for a year or five years or twenty years and then for some reason you fuck up. As in failed to yield, ran a red light, didn't see the pedestrian, fell asleep at the wheel, didn't check their blind spot, lost control of the car fail. I can guarantee you that all the SDC test vehicles are better than 100% of humans at not rear-ending anyone.
If it's not coming officially it's coming unofficially with all sorts of assistants where technically you drive yourself. And people will ignore it, but we'll dismiss them as Darwin awards.
Richard Dabate, 40, was charged this month with felony murder, tampering with physical evidence and making false statements following his wife Connie's December 2015 death at their home in Ellington, Tolland County.
Dabate called 911 reporting that his wife was the victim of a home invasion, alleging that she was shot dead by a "tall, obese man" with a deep voice like actor Vin Diesel's, sporting "camouflage and a mask," according to an arrest warrant.
Dabate alleged her death took place more than an hour before her Fitbit-tracked movements revealed.
Granted, you're not making it worse in any way by representing it with a union.
More to the point, you can't make it better by avoiding using a union. Because it's optimum as is.
The right tool for the right job.
pretty much the essence of obscure legacy cruft.
The job is the job. I have no problem using the right tool for the job.
This is the laptop. I'll admit, I can't really evaluate battery life as I never really use it unplugged for more than an hour or so. As one would expect, it will vary with workload and yes, I've had it nealy death after just over an hour, but I've also experienced the same with my 2014 rMBP; I've also never topped 5hr with that rMBP, but I've had that PC over 80% after an hour.
I use my laptop unplugged for at least 3 and sometimes as many as 7 hours at least once a week. Battery life is somewhat important in my use case. I'm curious how you have yours configured and what you run that you don't get at least 5 hours on battery. I have mine configured for power savings on battery, which means falling back to Intel graphics if possible.
Considering that it's pushing a much heavier GPU and higher resolution display, it really wouldn't surprise me if it didn't manage to win any awards for battery life. Lighter and faster than my rMBP, though, and I've noticed it runs a fair bit cooler as well.
It's pushing a significantly higher built in resolution than 2880x1800? (I've seen a few 3200x1800s but for all intents and purposes that is an equivalent load, 3800x2160 is generally far more expensive by the time you get comparable memory/disk hardware) What you're describing sounds impossible though - beefier GPU, higher resolutions and at least as fast as the MBP, but runs cooler and eats batteries? Something doesn't add up there.
You are just reinventing machine language where data, instructions, and address pointers can be mixed willy-nilly.
Because machine language varies hugely, and c varies little or none, when working on one platform and then another, c is a convenient low-level way to get as many advantages of working close to the metal (obvious ones are speed and executable size) as possible.
Higher-level languages merely try to introduce discipline and consistency to such practices.
Yes, they do. And in the process, they often cause the resulting product to suffer in speed and/or execution size (and the source code in clarity.) When "mere" means "the product is less good", I translate it as "not mere."
There are reasons to go one way or another. It's not as simple as "HLL's are always better." Sometimes even machine language is the best place to go, embedded controllers with limited storage and small tasks that must be accomplished efficiently, for instance.
The IBM purchase of ROLM gives new meaning to the term "twisted pair". -- Howard Anderson, "Yankee Group"