China strikes me as incapable of responding to bug reports, because a bug report puts the manufacturer in a bad light and that amounts to losing face.
Case in point:
I was maintaining a driver for a widespread SoC. The driver would flat out crash the Linux kernel during bootup (kernel oops and complete freeze) at every other kernel release, but only when booted off a specific hardware vendor's product. On other vendors' products based on the same SoC, no such problem.
I contacted the SoC's manufacturer, asking if that particular issue rang a bell. It didn't. However, their product specialist recalled that this particular hardware vendor had very pointy questions about hardware interrupts, back when they were building their BIOS image. As far as he could guess, the vendor had probably messed their build configuration and produced faulty BIOS images whose bugs were triggered by changes in the Linux kernel's other subsystems at every other release.
He gave me the name of a contact person at the hardware vendor, suggesting to report the bug to them. My e-mail was passed around from department to department – OEM support, Marketing, Sales, etc. – to no avail. One department assumed that I didn't understand some BIOS settings, another presumed that I was placing an order that would require a custom BIOS build. No, I'm reporting a defect in the BIOS sold in your products. I'm asking you to find the cause of the issue I've described – which does NOT affect other products based on the same SoC reference design that are sold by other hardware vendors, so it HAS to be a BIOS bug – and to please release a fixed BIOS image. At that point, someone with a modicum of English skills figured out what the word "defect" means and promised to contact me as soon as they found the solution. They never did. They also stopped responding to any further e-mail.
Retrocomputing, nothing else.
That somewhere is the issue; there aren't many images in distribution and the ones with original media hoard them rather than rip and share them.
Mostly lack of competition, but also Intel not selling their TB bridge chips to just anyone.
That was the case for me as well, while I used cheap-ass base stations. I wisened up and got quality gear, which works fine. I'm maxing out my four-year old 802.11n at 450Mbps at the moment.
Mine has speedometer information available to the car stereo. It adjusts the volume automatically depending on the speed the car is doing, so I haven't really had any need to adjust volume on it while driving.
There aren't many places outside US with capped bandwidth or particularly expensive internet connections; mobile and fixed.
This program is smarter than multiple slashdot commenters.
Which isn't very smart per se.
The efficiency of electric motors is around 90%, so I'm assuming the fuel-powered pumps have such a low efficiency it's worth using batteries instead of fuel to save weight. These are also unlikely to have rechargeable batteries, so the energy density may be an order of magnitude higher than let's say rechargeable LiPO-batteries.
About 17Hz or a bit more with most single DVI outputs, although 14Hz is the minimum required for DVI by actual spec. Twice that with two DVI signals. The display itself does the thing by partitioning the display; either 3840x2400@14+Hz or 2x1920x2400@28+Hz side-by-side or 4x1920x1200@60Hz in a 2x2 grid, capped by the display at 41Hz or 48Hz depending on the model.
I have one of these (rebadged T221; ViewSonic VP2290b), got it second-hand in 2008 or 2009. It's not just the display connection bandwidth, the 41Hz and later-model 48Hz limit is from the display internals. They use huge custom FPGA logic chips to drive the signals, which are apparently not fast enough for more than that, although some of them can be overclocked to drive almost 60Hz. Without these internal display limitations, four DVI cables have enough bandwidth to run one at 60Hz (4x1920x1200@60Hz).
I haven't bothered to drive mine with four cables, because with just two (1920x2400) DVI signals I get it up to 34Hz, but I've scaled it down to 30Hz, because it's evenly divisible by 60Hz. In normal desktop use, it's fast enough. For gaming and movies, there are other displays.
Eventually there'll be a point in resolutions when it's bandwidth-wise better to have the GPU on the display side and just run some future thunderbolt-esque long cable than running even higher bandwidths to the display. An 8k display with a resolution of 7680x4320 would require 50Gbps of bandwidth to be driven at 60Hz at 8bpp or 60GHz at 10bpp. The actual required data rate between the CPU, RAM and GPU is much lower nowadays, especially because most of the heavy lifting like rendering and video decoding is done by the GPU.
This article isn't scary. What should be scary is that cell companies cell anonymitized _geolocation_ data. That data can be used to deterimine: A) who you are, B) where you live, C) where you work, and D) who your friends are. Step #1. Look where the phone is, regularly at midnight. Step #2, cross reference with public records databases on property ownership. That get's 65% of Americans right there. Now check where it parks every day at noon. Place of work found. And so forth.
Well, someone who wants a modern car isn't buying an american V8 anyway.
Shouldn't maintainers of compromised systems be held liable for skimping on security?
Any programming language is at its best before it is implemented and used.