I think TidyLines is the best browser-based outliner I've seen. At least in terms of how it feels at the keyboard.

I certainly like the look of CoffeeScript.

Not quite sure what it's for yet. Is it just a nicer looking syntactic sugar on top of javascript? Or are there some powerful abstractions that simplify doing larger scale js work? (a la jQuery?)

XHP actually looks pretty cool. On the surface, it's just a cleaned up PHP. But the cleaning up (putting XML into the language) actually gives it some of the character I was hoping for in GeekWeaver.

The lessons of Mozilla Ubiquity

Giles Bowkett has a profound and entertaining blog-post, starting with some thought-provoking criticism of Joel Spolsky and Paul Graham; and then moving on to other questions of business models for blogging programmers.

Great exegesis of Ward Cunningham's maxim.

Another thing that I saw recently that looks pretty interesting : Fossil, a kind of source-control system with built in web-server and trac-like wiki and bug-tracking, all in a single executable file.

I've no time to play with this at the moment, but it looks very cute.

Wow! Dan Bricklin has still got it.

This is a really nice twist on the mobile notepad / todo list app. The UI looks brilliantly well thought through.

Joel on his "search engine for programmers".

More of Joel Spolsky's smart understanding of "social software" as both social and software. Now StackOverflow evolves to become a smart online CV for recruiters.

SocialCalc comes out of beta.

Growth of a Wiki.

WARNING -- THIS BLOG IS STILL SHUTTING DOWN ... PREPARING FOR REBOOT

EditGrid is going free.

Nice. WikiIsNotWikipedia

And by the same token, Wikipedia is not wiki.

Funny advert just popped up on a Google search :

Work in IT within weeks
Become a Microsoft Engineer Earn £35K+ No Experience Necessary

WARNING - this blog is going dark ...

To return to a theme I started many years ago, I commented on this excellent article about why web-site development has got so damned hard. (And remember when we all thought of web-apps as lighter and simpler than desktop apps? What happened?)

Anyway, here's my comment.

I think the problem is less the multiplicity of programming languages, than our insistence that we should always be separating our languages in different places.

This goes against the basic tenets of cohesion and coupling. We cluster unrelated activities together because they happen to have the same syntactic sugar, while separating tightly-coupled activities because half of them happen on the client and the other on the server. Why the hell should this implementation detail have to be reflected in our architecture?

What I'd like, controversially, is to be able to mix-and-match the languages within the same source file, grouping together the python, javascript, html and sql that actually has to work together in one place. I have no trouble dropping into regular expressions or similar DSLs from inside my main code, why should dropping into a layout or query language be different?

WARNING ... SmartDisorganized reboot coming ....

This is an absolutely brilliant summary of the virtues of PHP.

The important point is that these virtues aren't going away. By comparison this seems to miss the point. In 2020 we won't be programming the web with an advanced Python framework (wonderful as python is). We'll have something which does what PHP did for CGI or Processing does Java, ie. wrap a purpose built, sophisticated back-end (something like Google Application Engine) in a light, domain-specific language. That language won't look like PHP. It would be nice if it looked like Python, but I suspect Javascript is a more likely model.

But it will retain the virtues of PHP : none of this fussy separation of presentation and logic; easy discoverability of where URLs go; fast iterative development; big built-in library etc.


(Hat-tip, BillSeitz for the links)