3-Phase AC produces a smoother (considerably less ripple) DC current pattern when rectified than single or split-phase AC.

3 Phase doesn't require the return neutral, unless your load is very unbalanced. So they both require 3 wires to transmit.

And yes, it does appear to be a simple buck converter. Though you could probably use a Z-Source inverter too.

Yes, because the US cheats and uses 220 split-phase to provide 110 power. Most everywhere else that needs high power uses 3-phase, as it's smoother, easier to produce and rectify, and just as safe to transmit.

Why on earth would they call for 240V 60Hz? (almost) Nobody uses that. It's either 110V 60Hz (North America and colonies) or 240V 50Hz (UK, Europe and similar). And inverting to single phase is a lot harder than to 3-phase (and a lot less efficient).

And if you can still find them, the A1200 has expansion options up the wazoo, including RTG graphics, 16-bit soundcards, Ethernet adapters, dual-channel PIO Mode 4 IDE interfaces (To augment/replace the single-channel on-board IDE), Keyboard converters, even full PCI Backplanes or Zorro II/Zorro III/ISA/PCI backplanes which support many modern graphics cards, among other things.

The thing is, that was SCSI's fault, not the Amiga's. Dealing with DIP switches and termination was a problem no matter what OS you ran, or who made your hardware. Amigas had AutoConfig, which would (for Zorro I/II/III cards) allocate DMA, Interrupts and IRQs automatically at boot-time, along with auto-loading firmware and drivers. It was so good, in fact, that Intel copied it and called it "Plug 'n Play".

See, the thing is, that "Front panel audio" connection is running through a wire inside the case (Where all the RF interference from hard-drives and fans comes from) and is entirely unshielded. So it gets affected by everything going on inside the case.

Well, as the phone (that you slot into the "front" of the contraption) already has a suite of magnetometers, gyroscopes and accelerometers, it can quickly and reasonably accurately track head movement. There's also a hold for the phone's camera to look out, so it can be used for AR purposes (and the camera can be used to augment the head-tracking above).

Of course, what I'm waiting for is for someone to add some kind of "Steam In-Home Streaming" (or something similar) support for the phone, so you can run Oculus-supporting games on your PC and have the video sent over WiFi to your phone/HMD, which would be the perfect "Killer app" for this system. And the chances are, someone (Possibly even Valve) are working on this right now. It might exacerbate the lag issues (what with WiFi latencies and encoding/decoding latencies being added to processing latency), but it would be palpably better from a "freedom of movement" standpoint (and possibly a weight standpoint) than a Rift.

Okay, so here's a scenario for you. I've just built a nice new Ara phone. It has a computing module, a camera module, an LTE/GSM+SIM module, a 802.11a/b/g/n/ac module, 128GBs of storage, a touchscreen and a fingerprint reader.

It's the first time I've put this device together, with brand new parts out of the box. How am I meant to download the drivers? I can't use the WiFi, or the cellular modem, I don't have drivers for them yet. And I can't display any kind of configuration, because the display isn't set up either.

The "phone" has the main OS pre-loaded (I'm presuming a bare kernel on the Computing module, as that's what would decide what version of binaries and the like would be needed), so it can boot, but there's no functionality on it to mount the storage, or bring up the display, or even to start the WiFi and/or Cellular data, because there's no drivers for that yet.

The way I'm suggesting means that all the drivers are compartmentalized and available from first boot. The moment you slot a new module in it's ready to use. And while you can update the software onboard, you don't need to download software to get the system up and running. The on-module flash would also be locked into read-only mode for regular operations, and only unlocked as read/write when an update is required.

It's called Autoconfig. Essentially, Autoconfig does IRQ and address assignment (And is so good at it that Intel copied it for their "Plug'n'Play" system), but Autoconfig does more than that. It also initializes the firmware and loads it in. And the firmware for each device then contains the necessary libraries to (at the very least) get the hardware running. So, for example, hard-drive controllers get their drivers loaded and the hard-drive becomes available as a boot device, network cards are initialized enough that PXE booting works, graphics cards are started up and displays initialized, sound cards are initialized, etc.

So, essentially, every piece of hardware would take care of it's own drivers and NVRam config. WiFi module has WiFi drivers on it. And so on. The configuration software was not included on-device, but there's next-to-no reason why that couldn't be on-device too, as the price of flash is extremely cheap these days.

1. Minecraft is written in Java, not JavaScript.
2. The MCP (Minecraft Coder Pack) already has a deobfuscator built in (kinda sorta)

Why is he proposing a hard enclosure for this? It would be a lot more practical (not to mention more convenient and lighter) to sew these into the covering flap of a messenger bag or similar (like he had), using easily-obtainable RGB LEDs on flexible PCB strips (like he was using) that are already sealed and watertight. The only difficulty would be sealing the connecting points, but that wouldn't be too much of an issue, and if you're going whole hog and making from the SMT parts up (instead of repurposing already made components) you could make a square sheet of flexible PCB for the whole thing.

Also, aren't there laws against putting flashing/strobing/colour-changing signs and lights in front of people's faces while they drive? While better visibility is good, techno-disco-light-shows distracting all and sundry on the road is bad.

I guess you're not seeing the "Compare providers in your area" tab that shows at the bottom-right under the results graph? 'cause that showed for me, and listed both ISPs available in my area.

They did apologize for it. A few times. They've been showing DA:I around before it was officially announced, and they specifically called out "No more cookie-cutter levels".

Wouldn't it be a simple "Fix" to set up port forwarding to redirect traffic directed to port 32768 to a "dead" address. Then the port would already be allocated, and when the "Knock" arrives, the port is already in use, and data goes nowhere.