Aside from missing some very basic functionality (timestamps, schedule run history, pipeline/job search), it's quite common for bugs to have 3,4 & even 5 year ages on them before they even get looked at / scheduled. Even with the top tier licensing our company has with them, bugs regularly do not get addressed for years after filing. I think if they addressed these issues, there would be more people reccomending it to their peers, and this would definitely help uptake. As it is, I reccomend against it (and only use it as it's the company mandate CI system).

That was his plan though, to shutter these coal burning power plants and accelarate the shift to green technologies. Not offloading, shutting down entirely.

I love that they remembered to include a sturdy stripper pole on the edge of the dance floor. Very thoughtful.

Sounds like Symantec got caught doing some dodgy stuff (manipulation of a running executable), and got caught by the protections in place to stop just such dodgy behaviour.

I'm also kinda curious as to how much was blasted into space, and to where.

... when you forget to login.

"Beauregard Wattigney" Even a google image search confirms this...

Did you try turning it on first? I heard that really helps usability. ;)

Link to image for those unaware: http://upload.wikimedia.org/wi...

Noqia? ;)

When taken as a single entity, sure, but a thousand objects queued processed in parallel to each other, will greatly outperform a thousand entities queued in serial, even given overheads of thread contention, cache thrashing, etc. Set your granularity high enough and the cost overheads cease to matter. Statistically or otherwise.

As a senior software engineer, currently gainfully employed, I disagree. This one of many painfully simple operations that could be made parallel by anyone halfway competent.

This is actually a pretty simple task-oriented problem. Have a queue of objects that need to path to a new location. Each object is a self contained task, referencing outside information, but modifying information only inside the object (therefor needing no locking or contention of threads). For a thread in a pool of worker threads, pull the next object off the queue, find the path, store the path inside the object, place it in the queue of done objects. Loop. Not excessively difficult.

I agree, I assume he's breaking some DMCA law. Stupidly, he put his company affiliation on his profile, which is going to reflect massively badly on him. Nokia also has a huge "act ethically" policy as well, which will work against him. I'd be really really surprised if he didn't cop major repurcussions because of this.

Screw map parts, you can download map countries with Nokia's mapping solution, not just the current "navigation". The big differentiator with Nokia maps is the ability to operate without a data connection. Android can't do that yet (even with the saving feature).