Maybe I am missing something, but I haven't seen a solution to the noise problem of air traffic (especially anything rotor based).
Might not be an issue for long distance connection in sparsely populated countries like the United States, but I don't see it replacing trains in Europe until this is solved.
There is also the fairly obvious problem of safe operations in urban areas.
Rooftop helicopters were banned from Manhattan’s office buildings after a helicopter tipped over and decapitated waiting passengers, and then the blade fell to the street level where it killed another person.
Flying no matter how diminutive always has the issue of Newton's third law. This requires having large empty landing zones to be safe, or you risk having people land on you, which would hurt no matter how slowly they're coming in.
If you frame that issue as a purely technical one without ux/usability implications, where you'd absolutely want to have a (good) designer in the loop, your product is in trouble, too.
Replication is not the same as reproduction; I can replicate an API without violating someone's license or copyright (which I would by reproducing their work).
There is code I gift to the world that I license as MIT or similar and there is code I publish as a means for furthering what I perceive as a advanced society which I license as GPL or similar.
I don't ask anyone to share my ideals but conflating these two is dishonest.
Might not be an issue for long distance connection in sparsely populated countries like the United States, but I don't see it replacing trains in Europe until this is solved.
reply