obtu

The closest semantics I found were the location hints: https://developer.mozilla.org/en/DOM/KeyboardEvent#Key_locat...

The problem is, only the keyboard hardware knows where the keys are physically located. The OS knows the layout and could probably expose the QWERTY-equivalent keys, which would be sufficient for not-too-exotic keyboards, but I don't know if that is available to applications in a way that is sufficiently portable for browsers to expose it.

Chromium seems to expose this to Pepper plugins; here is the bug for making it an experimental js api: https://code.google.com/p/chromium/issues/detail?id=119362 Getting the lowlevel keycode is nonportable (I didn't find the implementation, but found switch cases and fallbacks if it doesn't exist). Conversion to a portable usb-hid-equivalent keycode is left as a stub in the patch that introduced the Pepper feature.

The reason would be security-related, as usual. I take it you deal with the clickjacking potential, and the potential for deliberate annoyances?

See the CNX list (Ctrl-F joshu), here in pdf form: http://omgfire.narod2.ru/SBC_comparison39.pdf

You mean repost. Cross-post would mean it was posted to a different site.

Reformatted:

me: so what were the reasons that nobody ever used typestate? was it just too cumbersome?

graydon: combination of incomplete and wound up not often able to benefit from much code-path-distance between site of check and site of constraint-enforcement.

graydon: I'm still unconvinced that could not be overcome

graydon: but the result is that using it has effectively caused all callers to do checks just before they call, which isn't much of a win

me: graydon: was typestate the whole reason you started rust in the first place? I'd be really interested to read a retrospective :)

graydon: no, I started rust because I was sick of hacking in C++ and wanted something with a saner compilation model, grammar, safety properties, concurrency properties ...

graydon: I'd used lots of other languages and kept not being able to use them in an industrial setting, because they failed to be similar-enough to C++ in important ways, usually.

graydon: typestate was just a property that hermes had that I liked because it looked like a way to statically optimize DBC, which I like in languages that have it

graydon: (sather, eiffel, some of the C# derivatives)

graydon: I tend to program over-defensively when left to my own devices. make copies of every datum to be local. make everything const. run a lot of internal consistency self-checks. etc. etc.

graydon: (the one habit I hadn't picked up yet, which I'm still trying to, is adequate unit testing and fuzzing ... sigh)

me: graydon: so are you confident yet that even if someone was forcing you to write rust, you would't be sick of it? :)

graydon: my experiences writing rust so far have been pretty positive. it has a number of the parts I like in other languages. the grammar is simpler, the compilation model is better, it's AOT and static, it has algebraic types, clear integer types, is eager and reasonably fast, doesn't force OO style...

graydon: and crucially: doesn't need to allocate / GC like crazy, so can close that residual gap on inner loops without having to hit the FFI

graydon: there are still odd bits we need to whittle down

graydon: oh also the safe references are lovely. and getting better.

Take this: http://users.teilar.gr/~g1951d/Symbola702.zip

NoSquint is pretty good for this as well.

It's also a reddit rule, though hard to enforce.

♥ and
💩 have a nice symmetry.

500 karma according to this infrequently-updated FAQ: http://jacquesmattheij.com/The+Unofficial+HN+FAQ#karma

What else could the defaults be, though? The good communities are smaller and better moderated, but they don't have the resources to police anyone who signs up for an account. As it is they get the users who bother to change their subscriptions from the default, and that's an useful filter.

Nudging the participants in some of the big communities into better commenting behaviour seems achievable (less users go vote in comment threads, most communities manage being self-policing), but driving out the meme generators isn't achievable from votes only. They are what the lowest-common denominator of the user base wants to see, and what they upvote.

On the other hand some of the smaller communities would benefit from more recruitment, particularly of dedicated users, but that doesn't have to come from the frontpage. Tapping into other social networks, via things like twitter sharing and per-subreddit twitter accounts (like StackExchange does), would be a good avenue for that.

highlight.js [1] does this, though by running highlighters rather than using some learning-based mechanism. It feels wasteful to run this on display rather than storage, though. SourceClassifier [2] also works, though with less languages. And here's [3] an implementation made with Bayes and Go.

[1] http://softwaremaniacs.org/soft/highlight/en/ http://softwaremaniacs.org/media/soft/highlight/test.html

[2] http://blog.chrislowis.co.uk/2009/01/04/identify-programming...

[3] https://github.com/octplane/go-code-classifier

A TV is actually worse than a monitor for most purposes, especially if you want their output to match a video signal: http://mjg59.dreamwidth.org/8705.html

Technically, the only exit condition on Kickstarter is reaching the funding goal (often set much lower than the expected proceeds). After that, the cool thing may materialise with lesser coolness or not at all, and an ambitious project may find their next incentive in venture capital.

Error correction is part of the spec (along with a reference algorithm for decoding a real-world image), so by keeping enough margin in the right places it's possible to embed a logo safely.

Steve Yegge's Google+ rant argues that Jeff Bezos forcing Amazon to implement everything as internal services allowed a services platform to emerge, and that platforms lead to success (the “because Bezos is smart” argument is a bit weak, though):

https://plus.google.com/112678702228711889851/posts/eVeouesv... https://news.ycombinator.com/item?id=3101876

https://plus.google.com/110981030061712822816/posts/AaygmbzV... https://news.ycombinator.com/item?id=3138826

Good idea to come up with a minimal implementation of intents on the caller side. Apple will probably block it if it threatens to become useful though, because that would challenge iOS Safari.

The BBC article touches on this, but the study does not support this conclusion (or any conclusion that could drive public health policy, really). It is lacking any accounting for confounding factors, like physical exercise, diet, health, or income.

Just to clarify, both courts and an as yet unspecified government agency will have the power to order content removed (by site operators, web hosts, and ISPs). Looking at http://translate.google.com/translate?sl=auto&tl=en&... , the criteria are open-ended (the list starts with objectionable stuff for the sake of framing the debate; the last bullet point says anything deemed unsuitable can be suppressed; links to the same content are disallowed as well). In practice I expect the motivation for this law is to crack down on political dissent, alternative candidates, and any platforms that may support them.

Another difference is that the use of a built-in compass eliminates the need for a badge.

What do you mean, direction? It can already orient itself, it's the primary use of the electronic compass that they are also repurposing.

The SIM and baseband have absolute control on the rest of the phone, which doesn't make sense except for enabling this kind of surveillance capability. False/partial shutdowns or spontaneous wakeups of the radio portion would probably be noticed by this point, so it doesn't make sense that either would be enabled except in a targeted way.

It would be harder maintaining a large collection of software outside of one of the major Linux distros. Debian/kFreeBSD might have a chance thanks to the GNU userland, but the archive is less well supported than with the Linux kernel.

All the commands are implemented on the remote end (hence the latency), and some of them look like they are a limited node.js reimplementation (git is mostly the real deal, though the command list is whitelisted). I would be interested in a version that runs locally in JS/Linux.

This isn't necessarily a problem. I can learn by immersion.

Good teaching shouldn't introduce too many concepts at one time, but giving incremental goals that require interacting with a few related concepts is ideal. Tediously spelling out all the details is good for a spec, but would hurt interest and motivation.

Indeed. According to the UN report on inclusive wealth ( http://www.ihdp.unu.edu/article/iwr via http://www.economist.com/node/21557732/ and https://news.ycombinator.com/item?id=4196895 ) Russia's wealth is all natural resources, and decreasing mostly due to a fast drop in human capital.

Well, these astroturfers are a message in themselves. They do exist in the English web as well, though.

Nope, it comes down to the generally agreed definition of the universe: the universe contains everything. If you want a border, there's the observable universe (everything in our past light cone).

NTP sends a special message to the kernel (using adjtimex), that boils down to: today you will insert a leap second. This isn't the same as clock drift, which gets smoothed out, it means a minute with a 60th second (in UTC) or with the 59th second happening twice (in POSIX). NTP servers need a leap second table ( http://support.ntp.org/bin/view/Support/ConfiguringNTP#Secti.... ), but most other systems only need to know the current delta between POSIX and TAI, and manage without a leap table.

Here's a raw list of those who voted for ACTA

ALDE: Newton Dunn, Takkula

EFD: Allam, Provera, Tzavela

PPE: Audy, Bendtsen, Berra, Cadec, Casini, Dantin, Dati, Deß, Florenz, Gahler, Gallo, Gauzès, Grossetête, Hortefeux, Juvin, Lamassoure, Langen, Le Brun, Le Grip, Lehne, Mathieu, Morin-Chartier, Motti, Ponga, Posselt, Proust, Quisthoudt-Rowohl, Riquet, Rivellini, Roatta, Sanchez-Schmid, Vlasto, Weber Manfred

S&D: Moreira

And those who abstained:

ALDE: Chatzimarkakis, De Backer, Hirsch, Klinz, Krahmer, Lambsdorff, Manders, Meissner, Paulsen, Reimers, Thein, Theurer

ECR: Ashworth, Bradbourn, Cabrnoch, Callanan, Campbell Bannerman, Chichester, Deva, Elles, Eppink, Fajmon, Ford, Foster, Fox, Girling, Hannan, Harbour, Karim, Kirkhope, Kožušník, McClarkin, McIntyre, Nicholson, Ouzký, Stevenson, Strejček, Swinburne, Tannock, Tošenovský, Van Orden, Vlasák, Yannakoudakis, Zahradil, Zīle, van Dalen, Češková

EFD: Rossi, Salavrakos, Vanhecke

PPE: Albertini, Andrikienē, Angelilli, Auconie, Ayuso, Becker, Boulland, Böge, Băsescu, Caspary, Collin-Langen, Correa Zamora, De Veyrac, Dehaene, Dorfmann, Ehler, Essayah, Estaràs Ferragut, Feio, Fisas Ayxela, Fjellner, Fraga Estévez, Gardini, Gargani, Garriga Polledo, Giannakou, Gräßle, Herranz García, Higgins, Hohlmeier, Hökmark, Iacolino, Ibrisagic, Jahr, Jeggle, Jiménez-Becerril Barrio, Jordan, Kalniete, Karas, Kariņš, Kelly, Klaß, Koch, Koumoutsakos, Kratsa-Tsagaropoulou, Kuhn, Kukan, Köstinger, La Via, Liese, Lope Fontagné, Lulling, López-Istúriz White, Macovei, Marinescu, Matera, Mato Adrover, Matula, Mauro, Mazej Kukovič, McGuinness, Mikolášik, Millán Mon, Mitchell, Muscardini, Mészáros, Naranjo Escobar, Niebler, Ortiz Vilella, Pack, Papastamkos, Patrão Neves, Pieper, Pietikäinen, Pirker, Preda, Pöttering, Reul, Rübig, Salafranca Sánchez-Neyra, Sarvamaa, Saudargas, Saïfi, Schnellhardt, Schnieber-Jastram, Schwab, Sedó i Alabart, Seeber, Sommer, Striffler, Svensson, Tatarella, Thyssen, Tıkés, Ulmer, Vaidere, Verheyen, Voss, Weisgerber, Wieland, Winkler Hermann, Zalba Bidegain, Zanicchi, Zeller, Záborská, de Grandes Pascual, del Castillo Vera, Šadurskis, Šťastný

S&D: Christensen, Correia de Campos, Costa, Jørgensen, Schaldemose, Thomsen

from page 19 of this document: http://www.europarl.europa.eu/sides/getDoc.do?type=PV&re...