681 karma · joined July 27, 2010
Video of Nano Hummingbird: http://www.youtube.com/watch?v=96WePgcg37I
Nano Hummingbird on AeroVironment, Inc's (the creator's) website: http://www.avinc.com/nano
An Engadget post on the thing (also lacking many expository details): http://www.engadget.com/2011/02/18/darpa-funded-nano-humming...
A Kurzweilai.net post on it (not many details here either): http://www.kurzweilai.net/nano-hummingbird-uav
Edit: Ok I've been snooping around for articles on this and so far I've found these:
http://arstechnica.com/science/news/2011/03/the-memory-virus...
http://www.physorg.com/news/2011-03-enzyme-erases-long-term-...
http://www.nih.gov/news/health/mar2011/nimh-03.htm
http://www.sciencenews.org/view/generic/id/70519/title/Enzym...
As far as safety goes...I agree that personal flight has a great track record. But it's difficult to say if this would continue (absent a beautiful autopilot system) if we gave out pilot's licenses to 90% of 17 year olds and filled the sky with millions of small aircraft.
Not trying to sound snarky here, but have you ever piloted an airplane? The pre-takeoff checks take a little while, require a good bit of technical expertise, and are absolutely required if you want to be pretty damn sure that your airplane won't fall out of the sky. Safety is, at times, overemphasized, but then again your car won't fall from the sky when it stalls.
If I'm not mistaken (please correct me if I am), a plurality (if not an outright majority) of web servers are run using an open source OS. jQuery/Prototype/MooTools together hold an obscenely high share of the JavaScript library market. The great majority of websites on the internet run some combination of PHP, Python, Ruby, many of those running open-source frameworks like Pylons, RoR, CodeIgniter, Kohana, web2py, Django, etc. A great number of developers code using Vim, Eclipse, or some other open source text editor.
And from the perspective of the user? It's hard to quantify this just by saying "Firefox" or "Chrome" or the "V8 JavaScript Engine". I think open source projects (like jQuery) benefit hugely from crowd sourcing their problems. By making their bug reports and code public, they allow someone like me to fork the project on GitHub, fix the bugs, and issue a pull request back to the master branch. They're basically fine-tuning their product without doing nearly as much work as closed-source shops without paying the person for fixing the problem. To the user, it looks like things get done quickly and bugs tend to come far less often (if the crowd sourcing is done right).
In my humble estimation, these are rather important considerations when judging the success of open source...and these are only web technologies.
http://www.khanacademy.org/#Precalculus
And their calc videos here:
http://www.computerworld.com/s/article/9209958/Bulk_of_brows...
A: Most of our nearly 3 million solutions revolve around specific technology questions, and the majority of those have a sense of urgency to them.
Huh? How does this differ from StackOverflow? Other than, of course, that those answers are hidden behind a paywall.
We switched to a premium model to keep out of the Venture Capital business (been there, done that, got the t-shirt). Companies like StackExchange couldn't do it without the VC cookie jar. Where's the model? Huh, Spolsky? (I’m sorry. Did that slip out?)
Maybe he hasn't noticed the ads running on every SO page? Or perhaps he doesn't know anything about how careers.stackoverflow.com's billing works (https://careers.stackoverflow.com/billing/checkoutnew)?
I hate saying things like this because it puts me into a position where it looks like I'm saying too much sooth, but it kind of looks like the EE guys are starting to miss the paradigm shift that's occurred and probably will continue to occur in "long-tailed" question and answer sites.
http://stackoverflow.com/questions/2500716/open-source-comme...
There are also lots of other discussions related to this on SO.
In my opinion: with disqus you get to be lazy. That's fine. I use it on my personal site. I don't think it allows for infinite branching (like on Reddit), but that requires a pretty nifty nosql solution, were you to do it on your own.
http://stackoverflow.com/questions/3644614/what-might-be-the...
Client input cannot reasonably well be verified, of course, but perhaps more importantly, once you get down to a certain zoom level, the advantages of caching the information almost disappears as the number of possible X, Y, and zoom levels starts increasing rapidly toward infinity.
The other problem is that JavaScript has issues with very precise floating points and very high integers. Check out this Mandelbrot viewer that I made:
http://janhartigan.com/creations/fractaljs
(please be kind...my site is still under construction [where's my gif??])
It might take a little while to render, but if you keep zooming in (and upping the iteration value in the input box), you'll find that eventually things just start getting pixelated once JS reaches its maximum level of floating point precision.
Are you sure there isn't something else going on?
And what greater inspiration for knowledge is there than properly-gathered statistics? All I'm saying is that you guys could do a lot of interesting things if you relied more on well-selected samples over multiple time series. I don't think your post was at all bad, but it leaves me begging for more information.
http://www.colourlovers.com/business/blog/2010/10/26/color-o...
And so while this is still a nice, shiny piece of infographic eye candy, I don't really see the scientific basis behind any of this. It still seems like cherry-picked data to me. Why does it matter that these companies' colors be analyzed compared to any of the thousands of others that were successful in the last year?
And I think it's also important to note that I'm not talking about speed of feature releases. I'm talking about speed of general releases. New Chrome features often go from conception to stable release in 2-3 months because of the development structure in which they are released. I wouldn't at all be surprised if the IE team have worked out these canvas issues already, but they just haven't released it (which is why I mentioned that the last beta release was in September).