"There is some concern that Apple will have a hard time recruiting a top-notch CEO because of Jobs's presence." reads quite ironically too given how things panned out.

I just wish that Logo+<Number> didn't require you to hold the Logo key for a second or so before you press the number. I want quicker switching between apps than that.

You need to wait if you want the numbers to pop up on the icons, if you just want to switch programs you can do it instantly.

While it is very true that Unity is slow to launch applications I regularly launch a browser with Logo+1 hitting both immediately and releasing. The browser is launched and the side bar never even makes an appearance. You don't need to wait for the side bar to slide out. :)

Something roughly equivalent to:

  s = set()
  for e1 in edits1(word):
      for e2 in edits1(e1):
          s.add(e2)

The one bit of sugar in Python that always throws me off. Since the inner argument is written first in the comprehension, my intuition is that I'll add the iteration statements as I expand out to a slightly-higher loop. Nope!

It's not necessarily the inner argument that's written first:

    >>> [a for a in range(3) for b in range(2)]
    [0, 0, 1, 1, 2, 2]

It's just that for every iteration of the inner loop, it is evaluated and added to the result.

Once you keep in mind that their order has the same meaning as with normal for loops it's not so tricky. You can even indent them that way to make that more obvious.

Having done substantive work in both, the most significant difference that for me favours Python is that every module explicitly imports the names that are accessible within its namespace (barring use of 'from X import *' which is generally discouraged). In comparison I found it a real pain to track down definitions of specific names in a complex chain of 'require'd Ruby code.

Some realities can't be distorted. RIP.

No, but iOS is a derivation of OS X, so you have to take all the iDevices into account too. Probably Linux still has the numbers.

Android devices alone are enough to more than offset all iOS devices.

http://mashable.com/2011/01/31/android-most-popular-platform...

Even were that not the case, the consumer handheld market is dwarfed by the rest of the embedded market.

You're linking to a chart that only talks about handsets when it comes to iOS, and ignores the iPod touch and the iPad. It was written in January and a good chunk of the iOS devices sold have been sold since.

According to Apple, at the time of WWDC, iOS was the largest mobile operating system, across all devices (using that standard since you said "all iOS devices") with approximately %44 market share to androids %35 market share.

Of course it is difficult to know for sure, because so many sources of stats only count phones (ignoring the iPad and iPod touch) and the stats for android are not very clear either with many manufacturers shipping large quantities of android tablets that have not, apparently, been selling thru to customers.

Ah, well in that case: "Even were that not the case, the consumer handheld market is dwarfed by the rest of the embedded market."

My guess is that even if 44% is 'all iOS' and android matches only to 35% of that, the remaining '9%' of iOS devices plus all OSX installs are dwarfed by the remainder of all (non-android) linux installs, which I think was the original point.

Out of curiosity, I wonder what OS Apple's embedded devices use, such as the wifi access points?

If you read the context, this isn't really a specific criticism of ssh, but rather a general criticism of Unix's network model (or lack of it). Maybe we should all be using Plan 9, but as we're not ssh helps a lot.

I know, I'm a long time plan9 user, I know what it could be like.

I think you're right that the members of a community give it its value, but I think you underestimate the influence of the software. Consider it like the decor of a bar - once the regular clientele are established it becomes less important, but initially people are drawn there because they feel an affinity with the look and feel. IMHO of course.

Is anyone using this? Is it any good?

So on the balance of comments here I decided to give it a whirl. Posting this from the app, looks pretty good so far.

It's ok. I wish he would do some updates though. There are some annoying bugs and I haven't ever seen this updated.

hey. I'd love to hear about these bugs! you can either post them in this thread or email me at grinich@mit.edu. feature requests are also very welcome.

Two feature requests:

1. Let me pull down the reply field to see the comment I'm replying to. Having to reply blind is frustrating.

2. Figure out how to make it so that I can select text from comments.

Instapaper support would be nice, but not immediately necessary for me.

Overall, I quite like it (better than iCombinator and trying to use HN directly). Only two problems I have:

1) It seems to crash on threads with too many comments... I'm guessing it runs out of RAM, perhaps?

2) I can't log in with my OpenID.

If you can let me know what threads it crashes on, that would be really helpful. I have suspicions that it's actually an issue with the parser, not memory.

I've had it crash on the more "popular" iPad threads recently, where there've been ~193 comments. I'm not sure how much you'd be able to do with this given how HN sends the data.

Ok. I'll check it out. Thanks.

It's seemed like it's anything with over ~100-120 comments, but I'll drop you a line the next time I encounter one.

"most people need a push in order to perform"

Perform for the benefit of whom?