I believe the car bombing you are referring to was the Church Street bombing, which took place in 1983 while Nelson Mandela was in jail and Oliver Tambo was leading the ANC. I'm not sure you can really say that he bore responsibility for that attack.
Before Mandela was jailed, when he was actively leading the ANC, he was careful to target only infrastructure and economic damage, not civilians. When Nelson Mandela was arrested, they were in the process of moving from that type of sabotage toward actual guerrilla action against the military, but were still not targeting civilians. Hmm. Escalating from boycotts and economic attacks to guerrilla warfare against the military; not too different than what Sam Adams did. What the ANC did after while he was jailed did escalate beyond that, but as far as I can tell, what he did and advocated never went much beyond what the American Revolutionaries did.
In the course of the armed struggle, a number of military
actions took place which resulted in the death or injury of
civilians, and where gross violations of human rights can
be said to have been committed, despite ANC policy to avoid
unnecessary loss of life. Police statistics indicate that,
in the period 1976 to 1986, approximately 130 people were
killed by ‘terrorists’. Of these, about thirty were members
of various security forces and one hundred were civilians.
Of the civilians, forty were white and sixty black.
A total of 130 civilian deaths is quite low for a violent conflict over that long of a period. That's far lower than the number of civilian casualties caused by the US in Iraq and Afghanistan. Heck, per year the US has killed more civilians in Afghanistan than the ANC killed in that entire period.
I don't endorse attacks like the Church Street bombing at all; I find them quite abhorrent. But you need to keep some perspective on this. "Terrorist", in many cases, is just a convenient label for particular people who we want to judge more harshly than we judge ourselves.
Neither did Nelson Mandela, if that's what you're implying.
To wit, the Church Street bombing (which is presumably what you're referring to by the Pretoria car bomb) by the MK happened in 1983. That's 20 years after Mandela was imprisoned.
Unless you have some credible evidence that he was somehow the kingpin behind all the violent activities of the ANC and/or MK during the time that he was in prison, I think it's fair to say you're wrong.
Note that Chrome for Android (and the desktop emulator) are very different than Safari on iOS. Even when they were both built on top of Webkit, they had different renderers and platform bindings (and the iOS binding was not open source, which caused some of the friction that caused the split). Now that Blink has forked from Webkit, they are diverging even further.
So while this means you can do basic mobile web development this way, testing that your UI generally works on mobile devices, it's not substitute for testing and developing on actual iOS Safari.
You learn a little more if you actually hover over the icons in the "Features" section (which is very poorly disoverable, I scrolled past it and then back again and on a hunch tried hovering on the icons). You actually find out what it is on the "Specs" page. http://www.brck.com/specifications/
The BRCK is a rugged, cloud managed, full-featured router
with built in failover and programmable GPIO expansion.
BRCK can connect to the internet through RJ47, GSM, Wifi
Bridge, as well as Ethernet Over USB via the GPIO
Breakout. It’s rugged build and cloud managed interface
make it ideal for “away teams”, monitoring systems in
remote locations, and businesses with challenging
infrastructure. BRCK’s GPIO breakout provides 20 pins for
digital and alaouge Read/Write as well as I2C, SPI and
UART. This, combined with BRCK’s Arduino Profile, make it
ideal for quickly connecting hardware to the Internet of
Things.
RJ47 is also a connector I'm not familiar with. According to this site http://www.accesscomms.com.au/reference/RJreference.htm it's for "Programmed data equipment connected to a key system where the registered terminal equipment is not compatible with electrical characteristics of tip and ring behind line circuit." which really doesn't clarify anything. Given that it's an 8 position jack, however, I think that they meant the same thing as "RJ45" or "Ethernet"; but they don't seem to be good at communicating this.
So, I get that so far this is just an Amazon publicity stunt and there isn't actually anything here to talk about.
But give them some credit. Most of these problems are solvable. You can build a drone with bumpers around the propellers and screens above and below, to solve the "sticking finger in the propellers" problem.
You can deal with the vast majority of the navigation problem by just getting enough altitude. Above a certain altitude, you don't suddenly see new unknown buildings springing up out of nowhere, and don't need to worry about navigating around power lines or anything of the sort. Just do the takeoff in a controlled area, rise up to an altitude high enough to avoid anything but a few pre-programmed skyscrapers and radio towers, and fly to your destination at that altitude.
And you can solve the landing problem by having someone sit in a control room and take over for the landing and takeoff from customer locations. Paying someone for two minutes worth of landing and takeoff is much cheaper than paying them for the full 30 minute delivery time, along with the expense of a full sized vehicle and insurance that goes along with it.
Everyone seems to worry about the liability aspect, asking "what happens when one of these falls on someone". But we already deal with liability issues with cars all the time. Heck, we deal with the issue with planes as well; planes do sometimes fall out of the sky and kill people, but you don't hear people saying that delivery by plane will never work. That's just built into the cost of delivery. Drones are much lighter, don't have tanks of gasoline, and flying in the air gives you much more open space than driving on roads. And you could probably add a failsafe that deploys a parachute if the drone loses power or otherwise start to fall.
The big problem is flight time. Batteries just don't have the energy density to support long flight times; you can build ultra-light drones that get an hour of flight time with a lot of care, but if you're building something that's actually going to carry packages, deal with wind, and so on, 30 minutes is probably the upper limit. That means that you won't be able do trips of more than about 15 minutes each way. Now, since you can go in a straight line, without traffic, that gets you further than a 15 minute car/bike delivery, but it'll still be limited to people who are fairly close to a distribution center.
Are there other types of drones other than traditional quadcopters, for example variable-pitch quadcopters [1], that can get more airspeed and thus cover more distance in 15 min?
What about using airplane-style drones (like traditional RC planes) + a parachute to land the package? And this way you could use nitro gas fuel to get better energy density (since you can use one big gas engine instead of having to use four tiny motors)
I have quite strong opinions about this. The only way to ensure efficient, high-load drone flight is to develop a hybrid design which uses wings to generate lift during cruise. The efficiency lost to the rotors is massive.
So I think eventually we will see tilt-rotor designs, where wings take over once the drone is airborne but the rotor disk is pitched horizontal for takeoff and landing. This massively increases energy efficiency, and makes it possible to go a lot faster.
The reason this hasn't been done with larger airplanes (the only prominent example, V-22 Osprey, demonstrates the difficulty), is that combustion engines makes the design prohibitively complex. But with electric motors, it should be very doable.
Wow, that's with a greater degree of mechanical simplicity than I thought possible. But this is exactly what I was talking about. Now if you can somehow reduce propeller drag at high horizontal speeds and also accomodate a payload and/or a larger battery and also handle adverse wind conditions, you'd have something really nice.
Sure, there are potentially other designs that will get somewhat higher speed, though at some point that will require enough extra power that it won't be worth it.
Airplane style drones can fly further, but navigation is more difficult, and parachutes will pose a lot more logistical problems than landing quadcopters (or, more accurately, multicopters; they used octocopters in the demo). One of the nice things about multicopters is how easy control and navigation systems are compared to something like an airplane or traditional helicopter.
The biggest improvement would be from better battery technology. Battery technology is improving, but very slowly compared to, say, transistor density.
I have no idea what GrabCAD has to do with this, or what the GrabCAD challenge even is.
I don't see why Elbonia would necessarily represent Estonia. It's a fictional country, that represents all of the small, relatively poor, Soviet Bloc states that people in the US don't know much about; Estonia, or Latvia, or Albania, or Moldova, or Slovenia.
This just seems like some false outrage to garner hits for his site.
You're right! Hence emphasizing my point about Americans (like me) not knowing much about them. After checking Wikipedia, technically Slovenia was briefly Eastern Bloc as part of Yugoslavia between 1945 and 1948, but after that split and was independent of the USSR. For some reason I had thought that it was an Eastern Bloc country for longer than that.
This was designed by Chuck Moore, the inventor of Forth, and who's still doing work in this space, except instead of a single very simple core like this, he's making chips with 144 extremely simple cores. http://www.greenarraychips.com/
Ah, that explains the almost non-existant explanation of the design being a stack machine. :) I was a bit surprised when it said something along the lines of "the processor has OVER but not SWAP"; those are very stack-centric instructions.
Also, the "M" in MISC was never explained which irked me. Is it a pun, as in "miscellaneous"? Or "minimal"? It's strange to propose a name that feels a lot like a new acronym, but never spell it out.
The quote from "Surely You're Joking Mr. Feynman" explains it better. This Wikipedia article is pretty bad.
One mechanical engineer at Frankfort was always trying to
design things and could never get everything right. One
time he designed a box full of gears, one of which was a
big, eight-inch- diameter gear wheel that had six spokes.
The fella says excitedly "Well, boss, how is it? How is it?"
"Just fine!" the boss replies. "All you have to do is
specify a shaft passer on each of the spokes, so the gear
wheel can turn!" The guy had designed a shaft that went
right between the spokes!
The boss went on to tell us that there was such a thing as
a shaft passer (I thought he must have been joking). It was
invented by the Germans during the war to keep the British
minesweepers from catching the cables that held the German
mines floating under water at a certain depth. With these
shaft passers, the German cables could allow the British
cables to pass through as if they were going through a
revolving door. So it was possible to put shaft passers on
all the spokes, but the boss didn't mean that the machinists
should go to all that trouble; the guy should instead just
redesign it and put the shaft somewhere else.
So, a shaft passer really does exist, and really has been used. But for this example, of someone designing a machine that has one axle going through another wheel, the better solution is just to move that axle, rather than trying to actually build a wheel with a shaft passer on each spoke.
I'd like to see a reliable source, and ideally a photo/video of the device in action. I won't say it's impossible, but it seems like it would be hard to make sure the gear rotates smoothly instead of binding, and "Feynman says that a guy he worked with heard about it" isn't as convincing as it might be.
The shaft passer shown here has never been used in real life. The mechanism that's on each of the spokes of the cog has been used in real life to allow cables to pass each other (just imagine one of the spokes and the obstructive shaft are actually cables).
I considered it; I've done a good bit of Wikipedia editing in the past. The problem is, I have a hard time figuring out how to phrase it better without just including the Feynman quote. That's the only source, and it seems that the Wikipedia page is merely trying to re-phrase what Feynman said; there really isn't anything to the page other than Feynman's quote and the diagrams. As such, it's hard to do a good job rephrasing it rather than simply quoting Feynman.
If you can find other sources than Feynman on the shaft passer (and blog posts and forum discussion that are merely discussing Feynman don't count), I'll consider updating it with an improved description and reference to the other sources.
I object to that characterization. I rather like the taste of plain, unsweetened soymilk. It fills a very different niche than milk, however; milk is thicker and heavier (unless it's skim crap), and I'll have it with dessert, while soymilk is lighter and more refreshing. But I don't drink either on a regular basis.
Yes, various people have posted links to a variety of studies that have been done, and it seems like there is a good deal of individual variation, and that these kinds of effects only happen to people who are particularly prone and replace the vast majority of their protein intake with soy.