funksta

I'm pretty disappointed that they didn't update the DX. I was hoping for a DX with touch and decent PDF support, and would have payed $400+ for it. As it stands, it looks like they have orphaned it instead.

My hat is off to Google; the progress they have made with Chrome (in terms of both marketshare and features/performance) in just 3 years is remarkable. Chrome has greatly increased my enjoyment of the web as both a user and developer.

It's a press release. The paragraph in question appears to be in all of Apple's releases.

A "quick and dirty" solution is to use django-celery with the django-kombu (http://pypi.python.org/pypi/django-kombu/0.9.3) backend. This stores the tasks in your database, rather than having to run a separate broker like RabbitMQ. I've been using this for a few months and it's worked pretty well.

My understanding (and the article reflects this) is that the "module pattern" generally refers to a function that is executed immediately after definition; ie: var module = (function() { ... })().

I'm guessing you're referring to Crockford's pattern (IIRC he calls it a "functional constructor" in JS:tGP), which is generally the same, but the function is instead executed when an object is instantiated with it.

It's a small distinction, but your drawbacks don't apply to the module pattern as I understand it, since the function is only executed once.

Very true, there seems to be a cargo-cult mentality that the mere presence of "design patterns" improves the quality of your code automatically.

As I see it, the main benefit of design patterns is that they give developers a common vocabulary for different types of object composition. This can save time when reading code if an object's name or comments reference the design pattern(s) used.

I've always preferred:

    map! <C-h> <esc>:bp<CR>
    map <C-h> :bp<CR>
    map! <C-l> <esc>:bn<CR>
    map <C-l> :bn<CR>

This lets me keep my fingers on home row. Combined with MiniBufExplorer [1], I find it provides a more convenient tab system than Vim's built-in tabs.

(edit) It also works in the terminal, which is a big plus for me. I like to have the same keybindings when editing remotely.

[1] http://www.vim.org/scripts/script.php?script_id=159

Sounds very similar to the section of The Pragmatic Programmer on "Tracer Bullets". There's an interview with the authors that has more discussion here -> http://www.artima.com/intv/tracer.html

The way I think of it is that the path that exists first (the target file), comes first.

It's kind of a dumb way to think of it, but it seems to work for me.

I think the learning curve tends to be steeper if you have to "unlearn" some of your preconceived notions from using a centralized VCS.

I would love it if the iPad met my needs, but I find extended reading difficult on backlit LCDs.

Interesting, thanks for the heads up. I'm going to wait for a device with a single, big screen though.

The Adam looks like it has some serious potential. Not sure how the Pixel Qi screens will compare to eInk for reading though.

Still waiting for an ereader with a screen > 9" and good PDF support. The Kindle DX is oh-so-close, but it doesn't support PDF table of contents or annotations. A touch screen would also be nice. Anyone aware of any other products that meet these criteria?