Slashdot videos: Now with more Slashdot!
The automobile industry coasted on that for decades. Identical car, different fenders.
No doubt so, but how about the cost of operations in rough country with poor access, where going in on foot is feasible (witness the illegals crossing it) but patrolling in ground vehicles is not?
Hence I think the real comparison should be: How does the cost of using a drone compare to the cost of using a helicopter in those same areas? I'd guess the drone is significantly cheaper.
Second, how long does it take a drone to patrol, compared to a manned ground vehicle in the same area? What's the total patrol cost per hour for drone vs 4x4?? (Don't forget to factor in the cost of the 4x4 as well as for the drone.) In rough country, a drone (or helicopter) can get an overview in a few minutes, but a ground vehicle might be forced to wind back and forth for an hour to reach the same point (and might still not get a view of the ravines). If patrolling a given area takes the drone ten minutes and the 4x4 an hour, which one is more cost effective?
How does it affect man-hours? The patrol is generally two men, while the drone only needs its operator.
How does all this affect insurance rates on their various equipment? Do reduced hours in use also reduce rates on 4x4s and such? (Certainly it will reduce maintenance costs.)
Lots of factors to consider, not just 'dollars per arrest'. We need to see spreadsheets and balance columns, not assumptions.
Oh and when I say they work great, I was kind of lying. I have a favorite example. A while back a developer I was working with wrote some Spring/Hibernate code to pull records in from the database and print a billing report. Soon as he handed it off to me, I thought "What happens if I throw 100000 records at this?" Well what happened is that it crashed. So I cut the number in half and it still crashed. Down around 30000 records, it started taking about half an hour and THEN crashing.
Turns out he was using the framework to pull all the records from a couple of different tables and doing the join in Java. The SQL join I wrote to test the code took a couple of minutes to run on a million records and returned the correct output. On a hundred thousand it was neighborhood of 10 seconds.
Now the Spring/Hibernate people will be quick to point out that you can edit some XML file or something and make the framework do a join for you, thus solving that problem. And that is true, if you know a fair bit about the framework. And you'd have to know a fair bit about all the other frameworks they used on that project, too. By the time you got done learning all the frameworks they were using to the level of detail where you could actually be that effective with them, you could have written the application they'd built 10 times over.
Fortunately this story has a happy ending. The team ended up deciding to run the original developer's code against the billing database several times a day so that it would never have so many records to process that it would crash, thus solving the problem once and for all!
if it wasn't this that got him it would have been something else.
Yeah, 10 years from now...
LOL, but seriously... what does "the head or tail of the web" mean?
Depends which way you look at it.
The text is really fucked up, the "reply to this" and "share" links overlap the last few lines of each post (win32 Opera 12)
>facebook is mostly a teen phenomenon
Unlikely. FB has proven to be the most handy tool for collaboration worldwide between ichthyologists to ever happen. I can't speak or other disciplines but it's changed the face of this particular science.
Tumblr needs this WAY more tan anything else. Of course that would affect half the userbase.
the problem is corruption. which is not our fault
any other great insights genius?