Who else has the rights to Batman and Bugs Bunny?

...by which you mean "quite a limitation for a terminal emulator window"; that's not the shell doing that, any more than it's doing select, copy, and paste in xterm or gnome-terminal or rxvt or Konsole or Terminal or....

And, yes, if it's using the same terminal emulator code that a cmd.exe window does, select/copy/paste is a pain, especially to those used to either the "middle button pastes the current selection" model or the Shift+(Control-C,Control-X,Control-V) model, as are used in many UN*X terminal emulators (or the Mac Command+(C,X,V) model in Terminal).

And by me in the last paragraph of the posting to which you responded.

There are the CPU issues, such as "what version of VFP does the processor have, if any?" and "does the processor have Advanced SIMD?". The NDK has an API that can be used to get the answer to those questions (and to similar questions for x86 and MIPS), and there are the "rest of the platform" issues. The former may affect applications, but the latter don't, so the VM isn't needed to handle the latter, nor are fat binaries.

Again, the "rest of the platform" issues aren't relevant here, other than perhaps screen size (iPhone vs. iPad). I'm not sure what processors Apple's used have in the way of floating-point or SIMD support, so I'm not sure what flavors of "fat" are needed other than "ARMv6 vs. ARMv7 vs. ARMv8-A 64-bit".

It would surprise me a lot, because Google doesn't design the SoCs that go into Android machines other than maybe those with "Nexus" or "Pixel" in the name, so they're not the ones responsible for the lack of backwards compatibility between Zombo's ZomboFone F1 and their ZomboFone F2.

There's no need for a VM to isolate differences between 32-bit ARM CPUs; if you want to support both 32-bit and 64-bit ARM with the same binary, or support ARM and x86 with the same binary, a bytecode interpreter/JIT is one way to do that, but you don't need it to support two machines using the same CPU or using compatible CPUs, and it's not the only way to handle it (you could do fat binaries, as Apple does in iOS, for example).

The issue in question is not with the ARM CPU cores, it's with the stuff around it in the SoC, and the OS (kernel, graphics layer) deal with that - applications don't have to.

Except what he was really talking about was x86-based "IBM-compatible personal computers", which have, in at least some layers other than the instruction set, a lot of similarity, vs. ARM-based {smartphones, tablets, embedded systems, etc.}, where everything other than the CPU may be significantly different from system to system.

That has nothing to do with the instruction sets, it has to do with the fact that x86 got its big boost from the IBM PC and the clones of it, which were all pretty similar machines so that MS-DOS and its successors would Just Work on them, while ARM got its big boost from phones/tablets/embedded boxes, where the vendor supplied some or all of the OS, and they didn't care much about having to tweak the OS for the next machine.

Yes, as the article you cite says, it's mostly, well, smaller broken-down micro plastics that can be eaten by fish and enter the food chain, not large items.

So it's not as if there's nothing wrong with that part of the Pacific, it's that what's wrong is not a just floating obvious garbage dump.

I read it as "Streaming Dongle" but just figured Google'd just had too much beer recently (you don't buy beer, you just rent it).

Only if every diabetic within range of your hacking device is using an insulin pump that your device can hack. Not all diabetics are on insulin, not all diabetics on insulin use insulin pumps, and not all diabetics using insulin pumps are all using the same model with similarly-hackable firmware.

No, it's not. Nokia is an independent company that sold its mobile phone handset business to Microsoft. They mainly sell stuff that's used to build networks.

TFA doesn't claim Nokia said anything about Google Fiber. All it claims is that the number Nokia's talking about is 1 Tb/s, and that "For comparison on the consumer side, Alphabet's Google Fiber embryonic US fiber-to-the-premises service is offering 1Gbps connections.", so the comparison is being done by ZDNet, not Nokia.

They also say "on the consumer side", so it's somewhat like Caterpillar saying some new haul truck can handle 500 tons and the article reporting on it saying "For comparison, on the consumer side, a Ford F-150 can handle 1 1/2 tons" - it's not as if somebody's going to use one of those big trucks to do residential construction, it's just there to give a sense of scale.

That's not the main source of increasing global temperatures. Particular means of generating energy release greenhouse gases, and with greater amounts of greenhouse gases in the atmosphere, the greenhouse effect causes increased temperatures.

+5 Funny.

OK, "from a Yahoo email address similar to one Musk has used in the past", but I'd still expect the CEO to be sending questions such as that from a tesla.com address; was the Yahoo address used to send more public mails, so that his e-mail address inside Tesla wouldn't be used publicly?

What, he didn't think the fucking CFO of Tesla wouldn't see an email from "elontesla@yahoo.com" and open it only to see whether it's advertising 1) a penis enlargement treatment, 2) a weight loss treatment, 3) an exciting business proposal, etc. and then forward it to Musk with the heading "LOL who is this moron?"