depends on Linux and C.

Not really. Over at mbed.org, ARM has a rather nice C++ library for its Cortex M series, which are really too memory constrained to think about running any version of Linux on them.

Or a more complex example:

aaa.c:

char a[] ="TEST STRING";

bbb.c:

extern char *a;

int main(int argc, char *argv[])
{
printf("%s\n", a);
return 0;
}

As well as a wrapper around jdb, Emacs (with the JDEE package) also supports JDWP (which is what the IDEs really use), for remote debugging and debugging inside server containers.

Also, as of 24.4, Emacs supports adb as a backend for its remote editing and execution functionality (aka tramp), so you can edit files and run commands directly on Android devices from the comfort of your Emacs desktop.

...and if they're touting this for the "internet of things", I'm guessing they've added a Low Energy form of PAN (which was always transparent to IPv6 anyway, being a lower network layer).

an odd idiosyncratic mix of left-wing and right-wing ideas.

So the Libertarian version of liberal then.

Aristotle held that heavy objects fell faster than light ones.

Aristotle was of course right, its just that for most everyday objects, the effect of buoyancy in the Earth's atmosphere is negligible compared to the effect of gravity. What Galileo did was separate out the two forces acting on the objects.

The small space rocks that shower the Earth at regular intervals are small because a big rock once collided with the Earth, sending debris into an orbit around the Sun that regularly intersects with the Earth's. Those rocks pose no current threat to the Earth, their damage was done at the time of mass extinctions past, or when the oceans were carved out, or what ever other distant past event they caused. The ones to worry about are the large interstellar rocks that haven't hit yet. So no, this does not help narrow the search for objects that threaten the Earth at all.

It doesn't really matter. Gorilla glass 2 is tough enough already to resist scratching by pretty much anything I have in my pockets with it. The problem is not the toughness, it is the strength which results in cracked screens.

Not via OBD2, via the OBD2 connector. Most manufacturers will do that these days because CAN is now mandatory in the OBD2 port to get realtime emissions diagnostics. But for programming they use proprietary protocols that are additional to the standard OBD2 protocols.

You could always try pretending to be in Ireland for tax purposes.

This only really works if you have a VPN with an exit point in Luxembourg or the Netherlands, and use tor over that to an exit point in Bermuda.

Pffft. Amateur conformist. I get my slashdot by telnetting to port 80 and requesting it by hand!

Jokes aside, but I've been doing HTTP/web stuff since 1994 or so, I'm very familiar with telnet hostname 80 :) I've even sent HTTP .9 requests for a production server.

Wannabes, the lot of you. I've been getting my internets by telnetting to port 70 since 1991.

It could also be completely closed source and proprietary. Because it's all Google's own code they can license it however they like (actually, I don't know if Google owns all the copyrights; I'm not sure how they handle contributions),

I thought the class libraries that are taken from standard Java are actually Apache Harmony. There may be modifications by Google, and there are plenty more libraries that are unique to Android, but they have not written everything from scratch.

You're confusing interfaces of physical devices that isn't copied by copyright (but perhaps patents) with an expressible form of information that is copyright protected. (like a written work, computer software, song, and others)

I don't see the distinction. The physical interface is defined by a drawing, and drawings are as much subject to copyright as the file of structured text that defines an API.

I'm not sure if you're trying to be funny here, or just lacking in knowledge about the history of Sybase.

The idea was to open up access to other card providers. With the secure element being in hardware, operators were controlling the provisioning, so only very few phones came provisioned for Google Wallet, and none with major credit card companies, because those companies won't bend over and accept the operators' demands for a cut.