The (or an) attraction of Twitter
As I was reading Sun documentation yesterday, I had a belated realization about one of the attractions ofTwitter: it is a public place to put snarky comments and quick reactionsthat are neither serious enough nor long enough for a blog entry, even avery short one.
Now, as it happens I already have social venues for these reactions, butthey suffer from two problems. First, they're not public, and second,they take more involvement than merely throwing something at Twitter,because they actually are social
My wishes for Sun's online documentation
I have some wishes for docs.sun.com , Sun'stheoretically helpful collection of online documentation.
Sun has a lot of documentation about how to do things with Solaris.Well, how to do things with specific versions of Solaris, for exampleone for each specific release of Solaris 10. This level of archiveddocumentation for each specific release is commendable, but it leadsdirectly to my first wish:
I wish that Sun had permanent URLs that were always the current versionsof any particular document; I would
My reaction to Solaris 10 update 6's ZFS changes
I've been talking about my wait for Solaris 10 update 6 for a while,because it promised improvements and bug fixes for various ZFS issuesthat had been giving me heartburn. Since it's been out for a while andwe've actually put it into production on one server, it's about time Idid a review on how its ZFS changes stack up.
refquotadoesn't actually solve our ZFS pool quota problem , but it was never going to; it turns out thatI failed
How LiveJournal is sticky
Given the recent commotion over some of LiveJournal's business decisionsand people's unhappyness with LiveJournal as a result, I've beenthinking about the various ways that LiveJournal makes itself sticky(and thus hard to leave, and so on). I think that there are threegeneral levels of LiveJournal stickyness, in ascending order:
- the simplicity and ease of use for individual users.
- the network effects: the more that people that you want to read useLiveJournal, the more attractive it is to be there and
Thinking about what you do with undo
In thinking more about undo issues , I think that thefundamental misconception of designing an undo system is to think of itas purely operation based, instead of something more complex (I don'tthink that it's purely time based either). Undo is only operation basedover the very short term, where you are undo-ing an immediate mistake.
I've been trying to think about what things you do with undo, ingeneral. So far, what I have come up with is:
- fix
Towards a better undo
Here is my growing theory: current versions of 'undo' functionalitygenerally aren't all that good. Having any undo is a lot better thannone, and having multi-level undo is a lot better than only a singlelevel of it (to the point where it's hard for me to consider singlelevel undo as 'undo' any more), but this is a long way from being reallyuseful.
(The problem with single-level undo are hopefully obvious: it's onlyuseful
The HTML tax (in Python, and in general)
The HTML tax is my name for all of those bits of verbosity that you haveto include when you write straight HTML, as opposed to something morecompact . What do I mean by that? Well, considerall of the things that you need for a well formed, standards compliantbasic HTML web page these days.
A relatively minimal page needs a doctype, a section witha and ideally a declaration for the charset, andthen the boilerplate of the