jankassens

Apple took a long time to approve Opera, but they finally did: http://itunes.apple.com/de/app/opera-mini-web-browser/id3637...

I wonder why they charge for the tools to develop on their platform.

Charging for the forums/bug tracker is probably a good way to keep people out who aren't that serious about development, but I don't get why they charge for XCode. It's not like they'd make any relevant amount of money off XCode.

That would avoid caching, an option would be an optional suffix like placekitten.com/200/100/2

Mailing list post announcing the blog series:

http://www.erlang.org/cgi-bin/ezmlm-cgi?4:mss:56379:201102:p...

There's no problem here. You can be pretty sure simple calculations like this (and multiplications with a power of 2 vs. shifting etc.) will run the same machine code in the end.

The worst-case is indeed arbitrarily long, but the amortized runtime can be analyzed.

See: http://en.wikipedia.org/wiki/Amortized_analysis

A Swedish advertising agency did just that. You could upload a photo of someone and this picture would appear all over the place in a video.

http://www.draftfcb.se/info/thehero/en

What I meant was a scientific approach to design rather than just designing what looks good. But than again every good interface designer should take that approach.

I'd say that this design is quite engineer-driven. It seems, their design is 'just' applied knowledge about perception.

The core algorithm is called "Operational Transformation". See http://www.codecommit.com/blog/java/understanding-and-applyi...

A unified documents folder just doesn't work as seen on OSX. Most filetypes are bound to a specific application anyway, so there's no point in a cluttered unified folder.

The Javelin JS framework used for Facebook Lite.

http://www.javelinjs.com/

The environment needs to be Turing-complete.

Sorry, I should have added Adobe.

Unfortunately, I can't edit the title.

all used.

"Won't be the only place, but we think it'll be the best place." -- Steve Jobs

A recording a friend of mine made: http://kassens.net/shi-shi-shi-shi-shi.mov

I've always used Colloquy, it's an almost perfect client ;)

Here's how I became a contributor of mootools (a javascript framework).

1. I stumbled upon the project pre 1.0, loved it's ideas, but my javascript wasn't good.

2. I checked out the code and loved the style.

3. I started hanging around in IRC where the core developers chatted about decisions and problems.

4. I read the source code and when I wasn't sure why some code was like it was, I asked in the channel. Either someone of the team explained why it's that way, or committed my minor suggestion.

5. That way I learned more and more about the language and the project. My suggestions became better. I loved to see my suggestions being picked up and used in the wild.

6. Eventually I got commit rights (though that wasn't important to me)

My advice is to just go for it. Join the IRC room, talk with the people. Help with bugs or documentation. It's easier to get involved than you might think, there are never enough people working on such projects.

You will be welcomed by the community!