This is true of any pointcloud system though. No system returns density though, so you still have to make assumptions about what is worth running into at what resolution. So if a leaf falls in front of your car, you don't immediately slam on the brakes.
I don't know of any vision systems that do object recognition immediately, in fact I'm not even sure that is possible - or desirable. I guess if you baked segmentation into the firmware it would serve as a fast classifier, but AFAIK nobody is even talking about doing that as you would need a very well trained vision library and classifier to deploy to FPGA.
I make the distinction because we build fairly dense pointclouds with monocular RGB cameras and VSLAM. LIDAR isn't required anymore. LIDAR is faster with lower error tolerances today, but nowhere near as cheap or portable. I suspect monocular SLAM will overtake LIDAR in the next couple of years as it's getting faster and more accurate everyday.
As you mentioned we'll have to see where economics takes over as cameras are much cheaper, but less accurate.
I'm curious if your camera-based solution is for outdoor or automotive use. If it is meant for outdoor use, how is performance with oncoming headlights, a low-horizon sun, or in snow?
The snow thing is interesting actually, but in a different way than you might think. Because we do loop closure it makes matching scenes that are temporally separated (eg. no snow vs snowy or occluded by leaves etc...) very hard.
This is true, as long as you're willing to treat everything your LiDAR sees equally. The problem with this is that you're treating, say, a patch of grass (which you might as well drive over), a rock (which you'd rather drive around) and a pedestrian (which you might rather stop for, as a moving obstacle) the same way. Object recognition is still a good idea with LiDAR. And I'm not even getting into noisy returns or "negative" obstacles (i.e. holes).
Disclaimer: has done research in object recognition with LiDAR ;)
This seems to be a common complaint about new technologies; people claim that somehow anti-social, violent or abnormal behaviour will be a problem merely because it is _possible_.
With lidars you won't be able to adjust frequency because that's not how lasers work. Well, you can with free electron lasers but nobody is going to be putting those in lidars. But a laser is directional in a way that a laser isn't. You will occasionally get some false returns but real objects persist from scan to scan in a way that noise doesn't. I've worked with a small fleet of lidar equipped robots and lidar cross talk never caused us any problems. Sunlight on the other hand could be a big problem but automotive lidars are all rated for the outdoors.
For military applications it's more useful to have one radar at high range/power than to have n radars at low range/power, while it's just the opposite for civilian lidar applications. So I don't see military radar SOP as evidence that this is inherently difficult.
Some LIDAR units give you "first and last", that is, the time to the first reflection and to the last one. For a solid surface, both values will be very similar. For snow, rain, and foliage, they'll differ quite a bit. This is used in aerial surveys, where "first" gives you the tops of trees and "last" gives you the ground. It hasn't usually been available for ground-based LIDAR units, but there's no reason it couldn't be.
Where LIDAR typically falls down is in adverse conditions (rain, snow, low sunlight in the horizon). There's a group at my university, MDAR, who is prototyping a tech to better overcome the adverse weather issues through a better laser sensing technique.
Here's an article with a little more technical information [1].
Disclaimer: I've done some part time work on market research for MDAR.
[1] http://articles.sae.org/13899/