Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!


Forgot your password?
Trust the World's Fastest VPN with Your Internet Security & Freedom - A Lifetime Subscription of PureVPN at 88% off. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. ×

Comment Re:If Apple built a Hololens we'd never hear about (Score 1) 107

Not really. They're both projecting 3d images in front of a person's face. Both require motion tracking of some kind to reorient the image as a person's head moves. It's just that VR headsets so far have used IR lights, dead reckoning and other methods to do the tracking while hololens went full head-on with image processing. It didn't need to be that expensive just because it was AR.

Regardless, it was stillborn because it was prohibitively expensve. And not very good for all the tech either.

Comment Re:If Apple built a Hololens we'd never hear about (Score 1) 107

The first version was so expensive and technically flawed that it's hard to see who it was targeted for. The Oculus Rift dev kits cost $350, the HoloLens cost $3000. Regardless of the technical complexity that accounted for that price difference, it still doomed the headset.

Comment Re:ECC (Score 1) 260

No boot ROM means that a hardware device constructed from discrete logic and analog chips directly demodulates digital data from the radio, addresses the memory, and writes the data. Once this process is completed, it de-asserts the RESET line of the CPU and the CPU starts executing from an address in memory. Really no ROM!

Comment Re:Until (Score 1) 374

Rust generates code which is different in performance than C or C++ code written correctly.

Most of Rust's safety is done at compile time and compiles away to nothing or is in the design of the apis that check you're not doing something dumb when you call them. So if you tried to copy a slice of a buffer in excess of a buffer it would panic but it wouldn't impact on performance any more than C code doing the same.

Obviously you can forego safety in C but that's the point Rust is trying to address - safety without penalising performance. That makes it perfect for IoT and its why the assumption that C can rest cosy because of IoT is a bad one. If I were writing any code for IoT I wouldn't choose C unless I had no choice. I might choose C++ assuming I could be sure of using only C++11/14 and nothing else. But I would choose Rust in preference to either of them.

Slashdot Top Deals

Any sufficiently advanced bug is indistinguishable from a feature. -- Rich Kulawiec