What is going on with that Wikipedia article. The first two sentences are written badly to the point of being incomprehensible.

Well dodged

The point about small displays being the same in many ways as big displays was great, until the rather confusing conclusion. If both have in common that they are more suited for consuming information rather than accomodating interaction, how is a smartwatch, a small display, an excellent tool for interacting with a TV?

The reviewer seems very quick to dismiss the gesture based UI. His primary complaint seems to be that navigating it doesn't work the same as existing smart phones. Any HN users have any experience with it who could comment?

A shame. I was at this hackathon and witnessed this pair working on the hack; very driven and talented hackers. This sort of activity should be encouraged from such young talent, not punished.

It was encouraged by the hackathon, since they won. It was punished by the business it inadvertently harmed. This seems like a reasonable outcome.

The question I have for this is, why not just use Node with Firmata on an Arduino? Anyone give me the apparent weakness of that setup that makes this more preferrable?

I've played with Arduino and the #1 complaint I have about it is that in order to do anything I have to learn a whole lot about electronics. With Tessel you just plug a new module and npm install and you're good to go.

Though swearing is also being shown to reduce pain. Perhaps a vigorous bout of mid-meditation swearing will reduce back pain during a long session.

It seems there is a lot of "startup weekend" events masquerading as Hackathons. A Hackathon shouldn't be about business, or funding; no one should be leaving that room with investors interested in funding their 24 hour hackathon idea. It's for fun, collaboration and learning. When one of the judges took to stage at Hacked.io in London and banned business pitches, there was a small cheer.

The developer mode warning only occurs on boot, as you say. Having owned by the ARM Chromebook and the Pixel since both were released, I've probably seen that warning less than 8 times since install. The Chromebooks very rarely need to be turned off, and the one time that does happen often, on update restarts, actually bypasses that warning.

It really depends what you want to do. If you just run a chroot inside the stock ChromeOS then what you say is true.

But if you're dual-booting to another Linux distribution or just replace ChromeOS altogether (that's another issue with the linked article: what it describes is not a dual-boot) you can't escape frequent reboots. Especially due to flaky suspend/sleep mode support in other distros.

True, but the chroot is by far the most common and most stable method, and the one targetted in the article. Though as you say, the title is wrong.

Yep, Crouton was originally made for the ARM Chromebook from what I understand.

True. We did it on pixel as well.

Yes you did! Posted from a Crouton'd Chromebook Pixel.