The Moto X, or an enhanced version of it? In addition to the now-standard voice control, it automatically detects when I'm driving and goes into a "driving mode" that will suppress some notifications and use text-to-speech for calls and texts.
Hardly "insightful". If corporate greed were allowed to take its natural course, I'm quite sure that plenty of companies would be happy to offer faster access at lower prices than I currently have available, but local governments won't let them. It's regulatory capture, not the profit motive, that keeps the incumbents fat and lazy.
I'm trying not to pick up any extra bad habits, and I figure having one MOBA is plenty.;-) I like the completely-free-to-play model, which Dota 2 also uses, and Valve's legitimate efforts to support their products on Linux.
Local friends got me playing WC3 DotA, and I moved over to Dota 2 when Valve got the native Linux client working reliably. I also keep Civ 4: BTS around when I really have to be unproductive but can't sign up for an hour-long game.
Depends on which level you label the "code". The way the PAL worked was that the firing parameters were stored encrypted, and the code entered was used as a decryption key. Bad code, random firing sequence (and a fizzle).
What the system does with the key labeled "Caps Lock" is controlled by the OS, just like all the other keys. Remapping Caps Lock is usually quite easy in any modern system; KDE's Keyboard settings page has options to make it an extra Control or more exotic things like Hyper or Super, and on Windows you can use RemapKey or AutoHotkey.
the site is remarkably content-free. In particular, is this just a nice implementation of SAP/RTP, and if not, why? Even AirPlay is just RTP with an obnoxious (and broken) encryption on the payload.
I'll pile on the Arduino bandwagon here. For somebody who knows software (specifically, C with a bit of kinda-C++ for libraries), it's quite simple to get started, literally just requiring plugging in the USB cable and clicking the "upload" button to send a program to the board. You can get "shields" (stackable expansion boards) like the already-recommended Motor Shield to handle high-power or specialized connections, and you get a USB serial port to talk to the Arduino board from a computer (necessary if your "simple" soccer robot needs vision processing). It's great as either a simple standalone controller or a scriptable I/O breakout board.
Oh, I'm completely with you: Developers should run QA, but there will always be bugs that slip through. I was responding to the AP's insinuation that Google should be catching all their security problems in internal QA but that Microsoft should get a pass for some reason.
Yes, there actually is a difference. In the United States, the consensus of the Supreme Court appears to be that there's a distinction between producing a physical object in one's possession (such as a key) and divulging information in one's memory. Among other things, giving up an encryption key or a combination to a safe is an admission that you did in fact have access to the contents, whereas a key might have been planted in your office.
I'd suggest taking a look at Eucalyptus, an open-source cloud management system that's compatible with the Amazon EC2 APIs and thus pretty easy to script and automate for production resources and any of the students who want to play with features like on-demand load balancing.
While there are a number of good tools out there for working with scalability, more important than any particular tool is building your application in such a manner that it's easily parallelizable. In a Web app, a core principle to keep in mind is that the more stateful the application server-side, the more difficult it is to scale, and so designing your application tiers in such a way as to decouple requests is key. Limit the amount of session state the server has to keep track of, and you'll be able to load-balance request handling smoothly.
To be fair, the blame regarding OTG lies mostly with Intel, which explicitly designed USB to be a master-slave protocol (requiring a host PC) to compete with FireWire, which is peer-to-peer and has a layer 2 that looks more like Ethernet. OTG actually does put the phone into host mode, but there's negotiation required so that the phone knows which state it's supposed to be in and two OTG-capable gadgets can still operate correctly with OTG-oblivious hosts.
I've programmed PICs in both C and assembly. Anybody who's looking at programming an Android phone in Java should be able to handle basic stuff on one. But there's a reason I put my "if" in anyway.
You don't appear to have read or understood the OP's question: He isn't looking for "the Linux experience" (whatever that is), he just wants a GPIO breakout box for a phone. The IOIO is that and just happens to be modestly hackable in its own right.
Of course nothing's going to operate at USB v3 Super-Speed. You'd have to be running custom FPGA hardware to get anywhere close. On the other hand, the IOIO seems to be about as close to what the submitter wants as is practical with cheap hardware.
The OTG is the latest IOIO. Ytai is still working on crazily trying to pack even more features on the thing (apparently, his goal is to fit in every single sort of IO that the ATmega is capable of), but the OTG is the current state-of-the-art.
Came here to recommend the IOIO, specifically the OTG version (which will happily work with a standard computer as a USB peripheral as well). It also has connections for three separate I2C busses, and (unless someone can point me to an existing one), I'm in the initial stages of building an Android app to manually send I2C messages to chips for development purposes.
Stallman's actually right on this one for practical reasons, and esr agrees for the same reasons. Among other things, determining what's "commercial" activity is notoriously difficult (write a hobby blog and put AdWords on it?), and there's not a lot of evidence to indicate that the NC licenses do anything helpful.
Flat-out wrong. Not only do tax rates vary by individual street address (and, as posted above, by different family members in the same house), products can be classified differently in every jurisdiction, and in some jurisdictions the tax treatment of a product depends on the other products or services it's sold with. This isn't a case of a ZIP-to-rate table and a UPC-to-boolean table; just figuring out whether an item is taxable at all requires a rules engine.
Besides the write performance Raven noted, the flash block cache has two additional advantages over more RAM: depending on your workload, it's entirely possible for a working set to take up most of the 16GB limit for many systems these days, and all the RAM in the world doesn't help you on system startup. I have the second-gen XT, and there's a noticeable difference in boot/launch times the second and third time a version is loaded over the first.
The code that I saw, which basically reached out of its container and hit the "retweet" button on itself, was definitely a clever hack.
The Moto X, or an enhanced version of it? In addition to the now-standard voice control, it automatically detects when I'm driving and goes into a "driving mode" that will suppress some notifications and use text-to-speech for calls and texts.
Hardly "insightful". If corporate greed were allowed to take its natural course, I'm quite sure that plenty of companies would be happy to offer faster access at lower prices than I currently have available, but local governments won't let them. It's regulatory capture, not the profit motive, that keeps the incumbents fat and lazy.
I'm trying not to pick up any extra bad habits, and I figure having one MOBA is plenty. ;-) I like the completely-free-to-play model, which Dota 2 also uses, and Valve's legitimate efforts to support their products on Linux.
Local friends got me playing WC3 DotA, and I moved over to Dota 2 when Valve got the native Linux client working reliably. I also keep Civ 4: BTS around when I really have to be unproductive but can't sign up for an hour-long game.
Pretty obvious typo for "can now be".
Depends on which level you label the "code". The way the PAL worked was that the firing parameters were stored encrypted, and the code entered was used as a decryption key. Bad code, random firing sequence (and a fizzle).
What the system does with the key labeled "Caps Lock" is controlled by the OS, just like all the other keys. Remapping Caps Lock is usually quite easy in any modern system; KDE's Keyboard settings page has options to make it an extra Control or more exotic things like Hyper or Super, and on Windows you can use RemapKey or AutoHotkey.
the site is remarkably content-free. In particular, is this just a nice implementation of SAP/RTP, and if not, why? Even AirPlay is just RTP with an obnoxious (and broken) encryption on the payload.
I'll pile on the Arduino bandwagon here. For somebody who knows software (specifically, C with a bit of kinda-C++ for libraries), it's quite simple to get started, literally just requiring plugging in the USB cable and clicking the "upload" button to send a program to the board. You can get "shields" (stackable expansion boards) like the already-recommended Motor Shield to handle high-power or specialized connections, and you get a USB serial port to talk to the Arduino board from a computer (necessary if your "simple" soccer robot needs vision processing). It's great as either a simple standalone controller or a scriptable I/O breakout board.
Oh, I'm completely with you: Developers should run QA, but there will always be bugs that slip through. I was responding to the AP's insinuation that Google should be catching all their security problems in internal QA but that Microsoft should get a pass for some reason.
Why single out Google? Shouldn't traditional software vendors have also run programs through QA?
Yes, there actually is a difference. In the United States, the consensus of the Supreme Court appears to be that there's a distinction between producing a physical object in one's possession (such as a key) and divulging information in one's memory. Among other things, giving up an encryption key or a combination to a safe is an admission that you did in fact have access to the contents, whereas a key might have been planted in your office.
I'd suggest taking a look at Eucalyptus, an open-source cloud management system that's compatible with the Amazon EC2 APIs and thus pretty easy to script and automate for production resources and any of the students who want to play with features like on-demand load balancing.
While there are a number of good tools out there for working with scalability, more important than any particular tool is building your application in such a manner that it's easily parallelizable. In a Web app, a core principle to keep in mind is that the more stateful the application server-side, the more difficult it is to scale, and so designing your application tiers in such a way as to decouple requests is key. Limit the amount of session state the server has to keep track of, and you'll be able to load-balance request handling smoothly.
To be fair, the blame regarding OTG lies mostly with Intel, which explicitly designed USB to be a master-slave protocol (requiring a host PC) to compete with FireWire, which is peer-to-peer and has a layer 2 that looks more like Ethernet. OTG actually does put the phone into host mode, but there's negotiation required so that the phone knows which state it's supposed to be in and two OTG-capable gadgets can still operate correctly with OTG-oblivious hosts.
I've programmed PICs in both C and assembly. Anybody who's looking at programming an Android phone in Java should be able to handle basic stuff on one. But there's a reason I put my "if" in anyway.
You don't appear to have read or understood the OP's question: He isn't looking for "the Linux experience" (whatever that is), he just wants a GPIO breakout box for a phone. The IOIO is that and just happens to be modestly hackable in its own right.
Of course nothing's going to operate at USB v3 Super-Speed. You'd have to be running custom FPGA hardware to get anywhere close. On the other hand, the IOIO seems to be about as close to what the submitter wants as is practical with cheap hardware.
If you choose an iPhone, you're knowingly going with a locked-down platform that explicitly forbids hobbyist accessories: "I want to develop an MFi accessory for personal use. Can I join the MFi Program? No."
The submitter, on the other hand, specifically stated "I don't care what phone platform."
And I've been spending too much time in Arduino-land lately. The IOIO is running a PIC (which can be reprogrammed if you're feeling frisky).
The OTG is the latest IOIO. Ytai is still working on crazily trying to pack even more features on the thing (apparently, his goal is to fit in every single sort of IO that the ATmega is capable of), but the OTG is the current state-of-the-art.
Came here to recommend the IOIO, specifically the OTG version (which will happily work with a standard computer as a USB peripheral as well). It also has connections for three separate I2C busses, and (unless someone can point me to an existing one), I'm in the initial stages of building an Android app to manually send I2C messages to chips for development purposes.
Stallman's actually right on this one for practical reasons, and esr agrees for the same reasons. Among other things, determining what's "commercial" activity is notoriously difficult (write a hobby blog and put AdWords on it?), and there's not a lot of evidence to indicate that the NC licenses do anything helpful.
Flat-out wrong. Not only do tax rates vary by individual street address (and, as posted above, by different family members in the same house), products can be classified differently in every jurisdiction, and in some jurisdictions the tax treatment of a product depends on the other products or services it's sold with. This isn't a case of a ZIP-to-rate table and a UPC-to-boolean table; just figuring out whether an item is taxable at all requires a rules engine.
Besides the write performance Raven noted, the flash block cache has two additional advantages over more RAM: depending on your workload, it's entirely possible for a working set to take up most of the 16GB limit for many systems these days, and all the RAM in the world doesn't help you on system startup. I have the second-gen XT, and there's a noticeable difference in boot/launch times the second and third time a version is loaded over the first.