alecperkins

I'm considering actually using the Tangle controls for the interactivity. They do a really good job of being accessible and unobtrusive. Right now the controls are just vanilla jQuery UI. I started with native `<input type="range">` for simplicity, but switched to jQuery for quick compatibility.

Also, how does the notation feel? The goal is a balance between functional/useful and simplicity. Ideally, the plaintext version is just as understandable.

Given that the technology in that film was designed by actual interface researchers, based on their research, it's no surprise that it continues to resonate so well. Also, sci-fi does have a tendency to inspire, or at least be inspired by, the leading edge of technology.

Said researchers now have a company, Oblong industries, that's basically making the Minority Report interface a reality: http://oblong.com/

The idea that small font sizes are acceptable because “users can zoom” is fucking ridiculous, and I am extremely disappointed to see it suggested here. That is absolutely the wrong attitude. If a user has to go out of their way to use your interface, you're doing it wrong. No question. Interfaces should bend over backward for their users, not the other way around. Yes, you can't satisfy every edge case, but the default attitude must not be “well, users can just use this workaround”. That thinking is why we have crappy interfaces. If that's your approach for building interfaces, please stop building interfaces, for the sake of the user.

Same. A hint that appears after a wrong attempt at the "before you move on" steps and a full explanation that appears after two would be very helpful, especially with steps 7+. Without those it feels like a puzzle instead of a tutorial.

That's a condition of selling on the Amazon platform. Doctorow also makes his most of his books available on his site, for free even, under a Creative Commons license in basically every format imaginable, eg: http://craphound.com/down/download.php

It's a running joke that Sheldon and others look down on Leonard as a scientist. The claim is often that his work is very "derivative". Even Leonard's own mother criticized the originality of his science fair experiments as a child. Also, the dynamic between Sheldon and Leonard can be seen as theoretical physicist versus experimental physicist. (Not to mention extending the layers of superiority when Howard, the non-PhD mechanical engineer, is included.)

As for Sheldon generally being a douchebag, the article does a good job of explaining his (partially deserved) sense of superiority.

A analogy even more accurate to this case would be: "Let's suppose you let someone store their stuff at your house, and they have previously pointed out a problem with the lock. You come back home and find them picking on your door lock with a lock picking tool. You ask him "what are you doing?" and he says "I'm just checking the lock I said you should fix is safe. I do it for our security."

There are "stories" to the right that are really pro-Scientology ads, but not marked as "advertisement". The whole thing feels slimy, not even considering the subject.

I'm afraid you ask too much of the Internet.

The criticism of drones isn't of the technology, but the attitude of those operating them. The article mentions that it doesn't put the operator's own people at risk, and is trying to point out that this creates a detachment from the consequences. Before, taking out a target required people on the ground in some capacity, actually carrying out the mission or just identifying the target. Drones undoubtably save the lives of troops on a per-engagement basis, but now that there isn't that risk, and without some process or oversight, it's becoming too easy to just pull the trigger and destroy some pixels on a screen.

Odd. It looks perfectly fine to me, in both mobile Safari and mobile Chrome. The text is completely visible, with a little padding on either side, and videos all slide nicely into the text column.

I like to take this one step further and return referenced objects with both their ID and their URL as actual objects instead of strings. This is incredibly helpful for working with the API in something like Backbone.js, because then there's no need for logic in determining if it is getting a list of IDs as strings or full objects. It's doubly helpful if the references are to objects of different types. The client simply loads the objects as given, and can do a sync if it's missing attributes it expects. (Of course, sending the full data in one request is usually preferable.) Also, the `url` property on the model just returns the `url` attribute instead of needing to duplicate the URL construction pattern.

So,

    …
    {
        'id': 123,
        'url': '/resource/123'
    },
    …

    …
    '/resource/123',
    '/resource/124',
    …

    …
    123,
    124,
    …

> If I had to run a monolingual web stack, I would choose Objective-C for the sole language.

This article is severely undermined by its conflating internet and web. Objective-C doesn't have a significant presence in the browser, and is consequently a useless language for achieving a monolingual web stack. The article demonstrates a complete lack of awareness of the frontend side of the web and assumes that iOS apps are this frontend. There is not a single mention of JavaScript, or even the word "browser".

It also seems to be overly focused on the idea of computational performance, when in many cases applications are IO-bound. The descending cost of compute power means this efficiency edge in computation is decreasing in importance. Also, no mention of things like PyPy? Overall, the article has a very narrow-minded and misguided view of the web.

It's less about ensuring that students are at school, but ensuring that they are counted. The school district receives funding from the state dependent on attendance. That's what is meant in the article by "it's all about money". With the cameras and now RFID, they can record that the student is on the premises even if they are not in the homeroom for attendance taking. (There are legitimate reasons a student may miss roll call.)

The catch in this is that having proof of voting a particular way makes a voter susceptible to bullying, or gives them the ability to sell their vote. The Wombat Voting system attempts to address this with a public-key approach: http://www.wombat-voting.com/

Are you sure you're looking at the redesign? It looks less like GitHub now. There are still similarities, but Bitbucket is thankfully starting to take on its own style.

I didn't mean to say "Python does it, so CoffeeScript is not a problem", but rather that both can suffer from too much indentation. CoffeeScript is a little more prone, given the callback-heavy nature of JavaScript, but similar treatment of surrounding whitespace is helpful in maintaining clarity. (Basic example: I find Python's standard of four-space indentation helps CoffeeScript readability, and prefer it over the popular two-space indentation.) And in both cases, excessive indentation is a useful signal.

Readability is very subjective and depends on the user's knowledge of the language, as well as personal style, or 'accent', if you will. Code written with, for example, leading commas in dictionaries instead of trailing commas just looks bizarre to me and is a little harder to read, to me, even though I like to do something similar and stack colons.

I do every day, both in CoffeeScript and in Python. I find things like braces frustrating, because I already keep it indented, and have to then manage the openings and closings. With proper 'aesthetics', indentation is perfectly readable. Plus, if something starts getting too indented than is readable, it's a sign that it needs to be refactored. (Whereas JavaScript looks messy even with otherwise sensible nesting.)

If you use anonymous functions a lot, it's amazing:

    result = _.map object, (val, key) ->
        foo(val)
        

    var result = _.map(object, function(val, key) {
        return foo(val)
    });

It's funny, because as a big fan of Python who has had to do a lot of CoffeeScript lately, I find CoffeeScript very similar to Python, and very readable. It's certainly more readable than JavaScript, when you don't get fancy. It's called "Unfancy JavaScript" for a reason.

Many of the issues raised in this article can be solved by "simply" not doing it (admittedly not always a real solution). Just because the language allows something to be done, doesn't mean it should be done that way. Our team has a styleguide that clearly explains good and bad practice, for CoffeeScript AND Python. (It's possible to do bonkers stuff in Python, too, just harder.) It includes things like: use explicit returns, especially when intending to return nothing; include parenthesis unless it's more clear without them (callback as arguments).

Yes, it'd be great if the language were more explicit and made it harder to do confusing thing. But, its core goal is being "just javascript", which prevents some of that explicitness. Also, the flexibility lets the real goal be clarity.

I find

    my_object =
        key: 'value'
        fn: (response) ->
            console.log(response)

    my_object = {
        key: 'value',
        fn: function() {
            console.log(response)
        }
    }

    someFn arg1, arg2, ->
        doStuffInACallback()
    , arg3

    someFn(arg1, arg2, ->
        doStuffInACallback()
    , arg3)

Interesting. Much more game-like than I was picturing. (I had in mind something like that old Choose Your Own Adventure series.) I guess the line between interactive story and game is pretty blurry. It's not clear what PlayStory is. The treatment of the feature list suggests a more story-oriented approach, less game-like.

The web seems like a perfect medium for doing really interesting choose-your-own-adventure story interfaces. It's odd that there aren't really any examples (that I could find) that are more than just links to different pages. I wonder if it's just because video games, which are in many ways an extension of choose-your-own-adventure stories, are so dominant. I'm curious to see what sort of interfaces PlayStory comes up with.

I was first amazed at the quality, then surprised that these were taken more recently than I expected, in 1910. Then, I realized that, duh, that was 102 years ago. It's strange how even 100+ years ago is getting more and more recent. (Obviously, that's how it works. But perception lags quite a bit.)

That there's any confusion is why this is a problem. Once you start getting into centralized, micromanegerial control of the content of applications, you have to handle all the details, all the edge cases. Law has the same problem.

My interpretation is that it's referring to actually embedding a tweet in a way that pulls it live via the API (or otherwise presented as a tweet entity), and that just quoting someone's tweet (like one would quote an article) is still fine (how could it not be?). I could be wrong.

These kinds of specific restrictions that aren't actually specific enough and really up to their whim are troubling. Twitter needs to be careful that their regulations don't become too much of a burden on their ecosystem. The vagueness and uncertainty of their rules is the problem.

Streams are more an attitude shift to match how people consume content than a substantial functional shift. They still allow for permalinks; it's possible to link to any tweet directly. Stream-oriented content is about acknowledging that pages and destination sites are the wrong units of content. Content needs to respond to platforms — more than just screen sizes. Content Management Systems need to be treated as true content management systems, not page management systems. Content == data. See: John Borthwick's comments on content as information; Substance.io and Prose; Medium; NPR's API; &c. Pages are a legacy format.

Vote with your money.

You can edit your own, and fork the gists of others. They're full git repos.

I'm really liking this use of gists as a backend to more specialized services (eg http://dabblet.com & http://codepen.io ). It's a nice, easy way to get a versioned document store without having to build out the infrastructure. Direct access to the "raw" form is a plus.

My favorite part is that they all come in iPhone or iPad wallpaper forms. No. 34 is my favorite card, and instantly became my iPad lock screen.