Yes, the IoT is coming... as soon as IPv6 is fully deployed with stateless autoconfiguration so we'll have network addresses for all the things.

I hear both Verizon and Comcast are really happy about the idea of offering routable addresses for everyone, without finding some way to monetize it.

Such delightful ambiguity. Would "they" happen to be the laws, or the government?

Then what the fuck do we even have it for?

So when he made his appearance in Kim Dotcom's "Moment of Truth" thing he did last year it was all information he'd already released? They certainly gave the impression it was shocking new evidence.

It think it's important to figure out how to use it before figuring out how to mass manufacture it - since they don't know the end result required by the manufacturing process until they figure out how to use it.

Graphene loses it's sought after properties when doped. It becomes useless for the intended purpose. Silicon is better than doped graphene.

The internet is a series of cats.
You pull a cat tail in New York, he know if it's for one of his neighbours and will pull the correct tail. If it's not he pulls the tail of a cat in another neighbourhood until a the right cat in LA meows.

You should have released all your documents at once, now they're old and out of date.
You left in June 2013, all your material is older than that.

As far as I can tell, the only reason you're drip feeding information is so you can stay in the media and Russia will keep paying your bills.

They are comparing a global economy (Apps) to a local US market.

What's the profit of global Hollywood sales?

Apple repeatedly said they would manufacture in the US should it be able to man those plants and that is not the case right now. There's no manufacturing plant in the US that would be able to sustain the volume requirements.

Tim Cook often commented on this. Best they could do for now was to build Mac Pros in US. It's a much smaller volume.

Primarily? Because it won't pass the testing without a lot of work. In particular, there are negative assertion tests on header files (some things are not allowed to be dragged into the namespace, and the header are promiscuous). There's also a whole bunch of testing having to do with full and almost-full devices. There are also signal issues and process group membership issues. For example, you can "escape" an exclusion group on Linux by setting your default group to one of your other groups; Linux overwrites the membership in cr_groups[0] as a synonym for cr_gid, and doesn't handle POSIX saved IDs quite right, either (Neither do the BSDs, so this isn't a Linux-only problem).

Last time I attempted to run the test suit on Linux as a lark, there were about 20K failures (mostly tests not compiling because of it bailing out over the header file issues. There are also some parts of the system that have been subsumed by systemd; this isn't intrinsically a problem on its own, so long as the system *also* supports flat config files as an addendum, at least for some aspects of logging.

Also, getting the UUCP to work over USB serial dongles is likely to be something of a bear, unless you make the HDB modifications for handling the "rung indicate" as a notification to take the shared file lock on the callout device so the getty's don't start trying to chat with each other.

Finally, there some considerable legal/licensing issues for the trademark.

I have got data from when 5MB H/Ds were introduced ON TAPE, written with tar that is still readable. Good luck reading your ST506 interface H/Ds written with DOS 4.2.