Follow Slashdot stories on Twitter


Forgot your password?

Comment Isn't HoloLens way more useful for this? (Score 1) 44 44

Glass, it seems to me, is inherently far more limited than actual VR systems like the HoloLens. With the HoloLens you could choose where to put the small square of information you can see, plus of course there are all of the options of overlaying more info on top of physical objects you can computationally recognize...

I guess one big draw would be battery life, Glass you would think would be a lot better in that regard than the HoloLens.

Comment When the Man In the Middle is You (Score 2) 52 52

Crazy that the phone is not just some kind of passthrough ,but instead somewhere in he binary contains enough rights to do anything it likes with your car... the device must be just convincing the app that OnStar said it was OK to use it's unlimited powers to unlock the car and start the engine or whatever.

On the other hand, perhaps that ALSO means the attack cannot work with any arbitrary car, but only with an instance of an app you have already paired to your car so it was given the right credentials? If so it's a much less serious attack than it would seem at first.

The real issue would be, if a rooted Android or iPhone device could have the car-specific credentials scraped, to use at a later time with thier own OnStar app.

Comment I know about me (Score 1) 861 861

but I need to stretch my legs and rest a bit after driving 180ish miles. so stopping every 3 hours is still roughly in line with typical driving practices

I enjoy the five minute stop to get gas every 300 miles or so in my own car on road trips. I do NOT enjoy a 30 minute stop every 200 miles... That's called a "breakdown".

That's the kind of thing that turns a 10 hour one-day drive into a 17 hour mandatory two-day trip.

It's not like that is so uncommon either, lots of families I know only really stop for lunch, otherwise they are driving very long distances per day with short refueling stops.

Something else no-one seems to consider is the vastly larger number of "refueling" stations required if most cars are electric, each car has to stop for 10x longer, at shorter intervals...

Comment Re:Streetlights useful to remark road in bad weath (Score 1) 289 289

Some would argue that if you can't see the road, you shouldn't be driving.

You shouldn't start driving.

But you should keep driving if it means the difference between arriving at shelter for the night or risking sleeping in a car in a blizzard with extremely low temperatures, with the constant worry another car might hit yours.

Comment Streetlights useful to remark road in bad weather (Score 3, Insightful) 289 289

I'm a fan of getting rid of streetlights but...

There is one way in which I can see they make things definitely less safe, and that is clearly indicating where the edges of the roads are in really bad weather - in a driving snow or rainstorm, there have been times I've been really happy to have the lights on other sides confirming where the road was, because it was not possible to see that clearly through the windshield.

Comment Yes it is what we need (Score 4, Insightful) 351 351

Think of the countless small ways in which knowing some code, or scripting has been useful over your life - sorting simple lists, renaming things in batch, formulas in a spreadsheet... etc. etc.

Even if most people will not be doing code professionally, it will help them do little things for themselves. It will also help them understand to some extent why software driven things behave the way they do, and even to make more informed choices as to software driven hardware they buy (and that is the future).

It's not like a flood of really bad programmers will get through most hiring barricades, already famously difficult to storm. They will go on to do things besides programming, where light programming can help them.

Comment Re:Change Is Life (Score 2) 147 147

It's not all that hard to stick with a toolkit version for a couple of months (or to be honest, even a project lasting up to 18 months is no big deal.

That depends on the system. If you are doing iOS development, while 18 months is possible it's not advisable due to every new version of XCode (one major, a few minor updates every year) having more advanced tooling, compilers, frameworks... furthermore you are going to have to use a beta version at some point to test and debug your software on for un-released versions of iOS that you have to make sure you work well on before they are released.

I see your point, I was more speaking to the attitude of people that want to spend years without upgrading the underlying technologies involved in building and running your project... the longer you wait the worse the transition is, and like I said in the meantime you are also missing out on things that could have made development easier or resolved bugs you had to fix.

"I'm not afraid of dying, I just don't want to be there when it happens." -- Woody Allen