To paraphrase, "I come not to praise the Browser, but to bury it." Because
the cold hard fact of application development is that the browser needs to
die. Immediately. It's already caused more than enough damage. This may seem
to be a harsh statement. After all, the browser was responsible for the
explosion of the Internet. It serves many useful purposes and people do
billions of dollars worth of business through it every year. Seemingly, I
should be praising the browser, not calling for its execution.
Nevertheless, the browser needs to go, and we all know it. It's the dirty
secret of the IT world, one we never like to talk about - as a mechanism for
delivering a GUI, the browser stinks.
Stinks isn't even a strong enough word. The browser was intended to deliver
text across the Internet, and it's good at that. So good that people began to
piggyback other things onto... (more)
Like many people in the industry, I'm torn over open source software. I'm not
opposed to developers creating software and deciding they do it for the love
of programming, and have no need for payment - if they want to give their
work away, I see no reason why they shouldn't be able to do so, although I
think the people who want all software to be free should first get uniform
agreement from everyone in the industry to work for nothing before they get
on that soapbox. Even though I run a magazine in my spare time, I make my
living designing software, and I personally don't want to... (more)
What's in a name? A rose by any other name will still smell as sweet. Well,
perhaps in the world of horticulture, but in the information technology
arena, I'm not sure that aphorism applies. I'm sure you all realize that I'm
referring to the recent purchase of Rational Software by IBM for
approximately $2.2 billion dollars. This acquisition leaves me wondering what
Rose will smell like a year from now.
Rational as a company helped define an interesting movement and market - that
of development by model. Its founders defined various modeling methodologies
into UML and codified it... (more)
Back in the old days, when you needed to communicate with someone distant,
you usually had to send a letter. There was no instant response, and there
was no way to tell when your message was received. Now we have always-on
e-mail, BlackBerrys, and assorted other devices to make what was once a
leisurely (or agonizingly slow) process instantaneous, and synchronous.
This issue is about the battle of two idioms - instant, synchronous
communication, as championed by the Remote Procedure Call; and asynchronous
communication (which may still be instantaneous, but doesn't have to be),
People who know me would generally agree I'm a straightforward guy - I pretty
much just like to move in the direction I've said I was going, rather than
try to move from side to side and finesse something. So when it comes to
technology, I tend to like to go with technology because it makes sense, and
I usually assume that most IT organizations work that way as well.
But when you look at a technology like Business Process Management (BPM), you
can see that the straightforward approach may not be the best, fastest, or
even most successful route towards deployment.
BPM is a tougher... (more)