
Hard core. Can’t believe I’m agreeing with Nick Carr (again):
By perpetuating a false dichotomy between the friendliness of consumer apps and the seriousness of business apps, all that Krigsman is doing is giving enterprise vendors cover for continuing to produce software that’s difficult and unpleasant to use.
It’s machismo mentality. “Our software is build tough, to use it you must be rough!” Color me unimpressed, but I just don’t buy this rationalization for lousy engineering. If you don’t care for the users, fine, just own up to it.
Open to all. One thing I’m looking forward to in 2008, is an end to the “Open” Document Format vs “Open” XML charade. Both formats were designed to promote a product; good for them, not for anyone who cares about their data.
In years of writing and editing I have yet to find a compelling reason to use anything but HTML. It edits well, ironically OpenOffice has a decent HTML editor (called Web Writer), not perfect but good enough. And it even prints out with high fidelity. You wouldn’t have guessed it if all you do is print from Firefox or IE, both implement printing as an after thought. But in Buildr, we take an HTML document combine with a print media CSS, render through PrinceXML, and produce outstanding results (PDF, unfortunately).
Kurt Cagle has a nice introduction to CDF and related standards. More about the Compound Document Format.
Age with grace. Can Java be saved from death by feature bloat? I really admire Java’s original design, the one centered around minimalism of the language. Back them it was a bold move and the right thing to do. It still is the right thing to do. Only thing that change, Java is no longer The language, just A damn good language. So don’t screw it up, let Java stay Java and age with dignity and respect.
The same sentiments, in pictures.
Two types of developers. Those who read blog posts about the two types of developers, and … you know how this joke ends.
And now, for your moment of Zen. The “Blog” of “Unnecessary” quotation marks.