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


Forgot your password?
DEAL: For $25 - Add A Second Phone Number To Your Smartphone for life! Use promo code SLASHDOT25. Also, Slashdot's Facebook page has a chat bot now. Message it for stories and more. Check out the new SourceForge HTML5 Internet speed test! ×

Comment Fines != Safety (Score 1) 258

So, the data tells us then that most drivers ignore the red light and push it by 0.3 seconds or so to "scrape through". If the priority was safety, as well as issuing tickets, the time between one route going red and the subsequent route going green should also be increased by 0.3 seconds as well to compensate for behaviour. This would have more of an effect of reducing danger than a fine after the fact...

Comment Re:Classic style (Score 1) 9

Broadly, building an ARM linux target via yocto, some in-house tools (portable C), a couple of GCC variants for other targets. Pretty standard stuff but the main thing is being able to able to address any potentially critical bugs and recompiling in the same environment at any point during the long lifetime of the system.

Comment Re:Classic style (Score 1) 9

I think that's a little optimistic - I'm not aware of any long-lived embedded systems where the environment is updated in sync with the outside world. In practice this is nearly impossible (or rather, financially infeasible). Look at embedded systems developed for aerospace / medical devices / safety critical control systems for example. Once the system is tested, you don't do any major changes to the development environment or code!

And yes that does end up with a support nightmare, hence the question :-)

Comment Re:Classic style (Score 1) 9

We're not talking about purely compiling an application but a complex environment for an embedded target that needs to be reproduced in a almost identical manner in order to avoid full system re-testing that presents a massive overhead / cost. (look at build systems such as Yocto for an example). It's easy enough to archive all the tools required to do the build and test installing them on a non-networked machine to check you have everything in the archive.

However, consider how you'll be able to exactly replicate this environment in 25 years time when you don't even know if you'll be able to find a working machine from the same era to run the host OS on and that's the problem in a nutshell.

Comment Some more info (Score 1) 134

News item from Leicestershire Police :

Interestingly apparently a 0.2% false positive rate. On attendance size of 90,000 that's 180 people mis-identified. This is apparently using NEC's NeoFace Watch system which they started trialling in the middle of 2014.

Comment Re:Why would the festival cooperate? (Score 1) 134

If you don't do what the police ask you to, you will not be able to run your event, it's as simple as that. This is often a financial issue for example. :

I could name several smaller independent festivals in the UK that have been made financially infeasible by large imposed policing costs and had to be subsequently cancelled. Many would argue that often the policing costs are un-warranted and that the police may use this as leverage to prevent events that they don't approve of but no one has demonstrated this successfully to date. Certainly however it's true that there is wild variation in the level to which different events are burdened by the police but of course this can also be attributed to other factors such as the quality of their pre-event planning / paperwork and the differences in approaches that different regional forces take.

Personally however, as both and event professional and an engineer, I'd like to know whether this was imposed on Download as a condition of their license, and if so what their justification for requiring it was. Secondarily I'd like to know how it is that they have been allowed to do this on the quiet. Certainly I believe that storing images of peoples faces would be covered under the data protection act.

Submission + - A development environment still usable in 25 years time? 9

pev writes: Working on an embedded project that will need to be maintainable for the next 25 years. This raises the interesting question of how this can be best supported. The obvious solution seems to be to use a VM that has a portable disk image that can be moved to any emulators in the future (the build environment is currently based around Ubuntu 14.04 LTS / x86_64) but how do you predict what vendors / hardware will be available in 25 years? Is anyone currently supporting software of a similar age that can share lessons learned from experience? Where do you choose to draw the line between handling likely issues and making things overly complicated?

Comment Re: Is it the phone or the stupid stuff installed (Score 1) 484

Really? You're implying that slashdot readers are properly technically savvy? Those days are long gone. If that were true, all these arguments would be presenting reproducible and well explained cases (like proper bug reports!) not vague anecdotal stories that can't be proven... Just sayin!

Slashdot Top Deals

"If you can, help others. If you can't, at least don't hurt others." -- the Dalai Lama