Monthly Archives: July 2012

Talking Technology: Earth, Air, Fire, Water

This post was inspired by two recent posts. The first, by Redmonk’s Steve O’Grady, argues that The Technology Industry Talks Too Much About Technology. It concludes with

If it’s true, and it seems self-evident here that it is, that software is eating the world, technology will only become more important moving forward. In that context, quality of implementation will naturally play a role in sifting the winners from the losers. But as we move forward, it is worth remembering that the best technology not only doesn’t win all the time, it may not even win most of the time. For better and for worse.

I read Steve’s post because I’ve been a big fan of the Remonker’s going back to 2004 or so. I first dealt with Steve on a conference call during my days in IBM Strategy, when I spent a few months as part of a small team investigating commoditisation,open-source software, and their possible impact on IBM’s software business. One of the team hired Steve to get his insight.

I saw Steve’s post in part as a challenge. To wit, do I have anything useful to say about technology today? That led me to thinking about another post I read just yesterday, one that came to me in an indirect fashion.

I twit from time to time, and every so often Twitter informs me that I have a new follower. I find the arrival of a new Follower both surprising and interesting. Surprising in that I can’t see why anyone would follow anyone except Andy Borowitz and his hilarious tweets. Challenging in that I wonder why on earth would anyone give a damn about my tweeting.

In this case I learned my new Follower was Matt Walton, aka @MattWaltonRED, CEO of RED Method, a software development company in Austin that specializes in mobile software.

I became quite excited when I noted that RED Method’s newest project is EventMethod, a new cloud-based product for mobile event management. I’ve been helping a friend build a website for his startup, and managing events is one of the requirements. (That’s the reason I wrote about Drupal few posts back.) I then went on to read some of Matt’s blog posts.

I was quite impressed with one of them, Why Should Business Care About Mobile?. Indeed, a simple two-word phrase, one I don’t recall seeing before, gave me new insight into the state of software today, and some possible opportunities for the technology we are working on here at HARDBOL.

So let’s talk Technology. To keep it simple, let’s look at one simple question:

What is the single most important element in the computing industry today?

This is the kind of question that folks who talk — and write — about technology love to ask, as answering it takes lots of time, and may even put some bread on the table.

There are many options. Is it a single company? Say Apple, Facebook, or Google? Or all three together?

Or is it single hot technology? Smartphone? Tablets?

Perhaps new software? Node.js? HTML5?

And so it goes, more grist for analyst’s mill.

My own view can be expressed in a single word:

The most important element in the computing industry today is itself an element: Silicon.

Silicon is the second most abundant element in the earth’s crust, and the lifeblood of the computer industry. Silicon — in the form of sand — is the basis of one of the oldest yet still most useful, technologies: glass.

The ancient Greeks believed the world was made of four Classical Elements: Earth, Air, Fire, and Water.

Glass is the combination of two of them: Earth (sand) and Fire (energy).

Glass is magical. It is not a metal, yet it can be quite hard. It is impermeable to water and most other liquids. Best of all, it is transparent, and forms the windows that bring light into our homes while keeping the wind and rain at bay.

Glass, like any technology, can be abused as well as used. Consider, for example, the Window Tax introduced over three centuries ago:

The window tax was a property tax based on the number of windows in a house. It was a significant social, cultural, and architectural force in England, France and Scotland during the 18th and 19th centuries. To avoid the tax some houses from the period can be seen to have bricked-up window-spaces (ready to be glazed at a later date), as a result of the tax. It was introduced in 1696 and was repealed in 1851, 156 years after first being introduced. Spain and France both had window taxes as well for similar reasons.

Britain not only adopted the Window Tax — which condemned generations of people to houses with a few number of small windows –but applied another technology, in the form of the Industrial Revolution, to spend well over a century perfecting the means to coat those windows with ash, soot, and other industrial effluvia, making it even harder for the hapless Brits to see outside. Witness London’s Great Smog of ’52, the worst air pollution event in the history of the UK. Over 12,000 died.

Silicon, the key element in glass, is also the key element in modern computing, for it has the physical properties that enable the fabrication of transitors measuring a few nanometers across upon a silicon substrate. We use these transistors to assemble gates, registers, memory, and the other components of the modern microchip.

Within the last twenty years, a new form of glass has become another key technology in computing: fiber optic cable.

Or as the ancient greeks might have expressed it:

Earth (silicon) + Fire (energy) = Glass
Earth (silicon) + Fire (heating) + Water (cooling) = Wafer Substrate
Earth (silicon) + Fire (energy) = Fiber Optic Cable
Fiber Optic Cable + Fire (radio) + Air = Wireless
Computer + Wireless = Mobile

Within the last five years, silicon in the form of glass has emerged as yet another key element in computing: the glass display of a smartphone.

This new use of glass has changed the nature of computing itself, at least for the vast majority of users.

Ten years ago everyone used keyboard and mouse to create and manipulate information viewed through a glass screen. Today most people compute not by looking at a glass screen, but by touching a glass screen.

It was while reading Matt’s post that I came across the phrase “surface computing.” I don’t recall seeing it before, but I instantly knew what it meant.
See Surface computing and Surface Computer — a surface computer is a computer that interacts with the user through the surface of an ordinary object, rather than through a monitor and keyboard — and Multi-touch.

Since I found it so insightful, I here take the liberty of quoting much of Matt’s post:

First, in order to answer this, let me ask another question. Why should anyone care about surface computing? After all, maybe only a few have ever even heard of this, and even fewer, perhaps, even understand how surface computing changed mobile, and how mobile will change surface computing.

But, if you just look past the novelty of the mobile smartphone device, and really look at what has happened, you’ll notice that it isn’t the phone capability that has changed, it’s the computing capability within a very small device wrapped up in a sexy package–all accessed by the tiny tip of your skinny fingers, or in my case, fat fingers.

The bag phone, or the famous phone from Wall Street, the Motorola Brick, represented two technologies converging: the microprocessor and the signal infrastructure owned by the telecoms. Within 20 years, the phone had flown through its evolution, at a crazy speed. What I find interesting is, however, isn’t the evolution of the phone, but the ever-increasing speed of the signal, of the connectivity. Seriously, think about the connectivity coupled with our smartphone devices today. They are fast, very fast, and they are only going to get faster.

What the mobile device essentially does is that it provides a link to a key, to an identity that you control, that you own. It is just like you having a set of keys for your existence in that the device will become that for you. This, however, I will save for another, more in-depth, blog entry. But, because we are now coming to a convergence of tiny microprocessors, as far as ram and network connectivity are concerned, the market struggles with UI.

If the mobile device is the key to your identity, it is essential that you be able to access that identity quickly (connectivity) and easily (UI). How are people supposed to click on such tiny buttons, became the concern. Speed and connectivity were already solved issues thanks to telecoms, so we trained a whole generation of people to type on a little keyboard on a mobile phone to fix the secondary issue.

Then, in stepped Apple, giving us what we truly needed: a touch screen. It was, at the time, something only a very few were talking about in meetings, on blogs or vlogs. It was an area in which people were experimenting, but where in which they couldn’t crack the code for a commercial product. The solution was surface computing.

Overall, I’m sure you can find a few people with differences of opinion about what surface computing really is and how it will be used in the future, but you should care about it because it is the solution to all things mobile. Without surface computing, connectivity, speed, size, none of it would matter.

Surface computing changed the history of mobile and took it from a telecom business and brought it back to the tech world. In my humble opinion, we started surface computing back with the first touch screen, and it is just now beginning to mature.

Not even telecoms can predict where this one is going. Can you?

This expresses well a vague feeling I have had for some time. As a programmer for over forty years, I know the game has changed, and in a much more dramatic fashion that such “innovations” as object-oriented programming, Java, HTML/XML, and so forth.

The notion of “surface computing” captures the new paradigm. We no longer type on a keyboard and look at glass. Now we touch touch that glass, tap on it, rotate it, and talk to a microphone placed near the glass.

There is yet another great change going on.

Until now the majority of users have used keyboards with English characters and looked at English text, in the form of ASCII, displayed on a glass screen. It doesn’t take too many more characters, say several hundred, to display the languages commonly spoken in Europe and the Americas.

It is only a matter of time — and it may even have already happened — until most of the content of the Internet is not in English, and within the same span most of text displayed on the world’s smartphones will not be in English.

There is an additional change that has already happened, but has gone largely unnoticed.

Today’s smartphones have the computing power of a 1990’s supercomputer. That this is not fully appreciated can perhaps be explained by noting that the processor speed is not apparent because most applications have as their workload a series of simple exchanges of information with a web server, the speed of which is much slower. Also, the base languages of the dominant players — Apple’s Objective C and Google’s Java/Darvik — are both complex and too low-level for most programmers. There are lots of cycles left to permit the use of higher-level languages to write mobile applications.

With great change come both challenges to established players and opportunities for new entrants.

To me the great opportunity is to enable the use of higher-level languages, first by working at the hardware level — just above the silicon substrate — to make them more efficient; then by promoting their use to write applications at a higher level.

Any such system must thus provide full and efficient support for Unicode. A Smartphone user will not learn another language just to use it. Any taint of a non-native language will be an invitation to competitors.

I’m not sure if I’m right or wrong on this, but I do expect to spend the next few years finding out.

In praise of git and its hub: Bug fixing made easy.

I got an email from Craig Wright earlier today about Linux SPITBOL:

Dave, I hate to be the bearer of bad news, but I think I have found a minor bug (probably mostly cosmetic) in the version of Spitbol for Linux that you recently posted.

If you look at lines 7938/7947 of v38.min, you will find two minor errors:

7938 *
7940 *
7942 DAC 25
7943 DTC /Macro SPITBOL Version 3.7/
7944 *
7946 DAC 4
7947 DTC /3.8.1/

I think that line 7943 should be 3.8.1 and not 3.7 (perhaps 3.8 would be okay)

I think that line 7946 should be DAC 5 instead of DAC 4

I am sending you my comments by private email instead of posting them on the blog.

Java programmer, Spitbol lover since college at Ohio State, and woodturner (hobby only)

He not only found the bug, he read the Minimal source, probably the first person to do so — except for old-time SPITBOL implementers like myself — in over a decade, and my new friend Craig even gave the correct fix!

This, by the way, is one of the reasons I *really* love open-source.

I put Craig’s advice into practice. I made his suggested edits, checked that SPITBOL still compiled, used his email as the basic text of the git commit message, pushed up the change to github, and then sent Craig a reply to his email.

All this took about five minutes.

The really nice thing is that github even makes the commit available as a separate URL. For example, see github commit 24e17d5bc730db168a6fe799012d3ece7d24041.

Not only do you see the commit LOG, you can also see the source changes that resulted from it.

This is *so* much better than how I did this over ten years ago in the Jikes days, when I had to extract text from email messages,fix the code, reply to the submitter, build a new release, run tests, create a tarball, update the web site, and so forth.

Today you just fix it, test it, and push it.

Your work is then automatically published in a form open to all, comments and source included, in a visual form very pleasing to the eye.

This is the kind of thing developers just love, and so it’s no surprise that the VC folks are starting to throw money at Github, because the VC’s know that *all* savvy open-source developers, and their code, will eventually be found at github.

The key point to me, as a developer, is not that github made my job easier. It is that by making it easier, and by displaying the work so well, github made it more likely that I would give credit where credit was due, and that is something we value dearly.

On having to pay over a thousand smackeroos to release SPITBOL on the iMAC for free

As noted in recent posts, I have just paid over $100 to enter the Apple iMAC developer program.

While I am able to develop SPITBOL releases for most computers I can think of using my trusty Unbuntu boxes, Apple has proprietary hardware, and so I just forked over an additional $900 to buy a refurbished iMAC:

Refurbished MacBook Air 1.86 GHz Intel Core 2 Duo

Originally released October 2010
13.3-inch LED-backlit glossy widescreen display

4GB memory
128GB of flash storage

NVIDIA GeForce 320M graphics

Built-in iSight Camera

I have thus paid over one thousand dollars out of pocket — and after-tax — so I can give away SPITBOL for the Mac!

And I thought open-source was free…

How Apple makes money with the GPL

See my recent post Why I had to pay Apple $99 (plus tax) to read their Mac OS Development License.

Why I had to pay Apple $99 (plus tax) to read their Mac OS Development License

I hope to release Linux SPITBOL for Apple’s MAC OS shortly.

I only did this after verifying that Apple allows the use of GPL-licensed software in MAC OS apps.

I first investigated Apple’s postion on the GPL a couple of days ago, by searching on “Apple GPL.” The available posts indicate that GPL-licensed code was NOT allowed. See for example the article by Steven Vaughan Nichols (one of my goto guys on all matters Linux and open-source) in January 2011: No GPL Apps for Apple’s App Store.

I sent this note and a query about the GPL to a colleague from my days CIMS who now develops Apple apps. He sent me an excerpt from their Developer License Agreement saying that it was ok to use GPL-licensed software, as long as I met the terms and conditions of the
GPL license, which I can easily do just by shipping the GPL-licensed part of my app with the app.

I decided to confirm this by reading the full text of Apple’s agreement, and so headed off to Appstore Development Guidelines, only to find the following

Developer Program License Agreements

The iOS Developer Program License Agreement and Mac Developer Program License Agreement details your obligations and responsibilities as a member of an Apple Developer Program. The latest Developer Program License Agreements can be reviewed in Member Center. Log in to Member Center (emphasis added).

I thus learned that I needed to login to the Member Center, and did so.

I then learned I had to pay Apple $99 (plus tax) to proceed further.

Simply put, Apple was asking for over a C-note just to read their developer license!

After suitable gnashing of the teeth, I went throught the signup process, including charging my credit card for over $100.

Turns out Apple does indeed now accept GPL-licensed code. Here is the relevant part of their agreement:

3.3.20 If Your Application includes any FOSS, You agree to comply with all applicable FOSS licensing terms. You also agree not to use any FOSS in the development of Your Application in such a way that would cause the non-FOSS portions of the Apple Software to be subject to any FOSS licensing terms or obligations.

Good news indeed, even though I had to pay Apple to learn it.

In any event, I hope to release SPITBOL for MAC OS soon.

Some say you can’t make money with the GPL, but Apple has definitely found a novel way to do so

“I’m on the phone with D-Link”

Alfred Hitchcock called it “The MacGuffin”.

I call it THE MOMENT.

THE MOMENT is when things change in an instant, in a dramatic, and sometimes life-altering, way.

For example, public events such as the attack of Pearl Harbor or 9/11.

Or, to give some personal examples, it can be a  single phrase or incident. For me, such MOMENTs include the day I learned I had been accepted to attend Caltech, my first view of the New York Skyline as I approached the Lincoln Tunnel after a non-stop cross-country drive during my sophomore year at Caltech, the fist time I encourtered Great Art directly a few days later, when I first visited the Frick Museum and viewed  two Vermeer paintings near the entrance, or the night a few days later when — looking out of a friend’s apartment at 93nd and Riverside,with a view of the Spry sign on the other side of the Hudson River that John Updike once wrote about — I vowed to live in New York City for at least five years before I turned thiry.

Some MOMENTs are yours, some you witness. For example, I recall from my days driving a cab in New York City a fare I picked up in the mid 50′s. A woman got in and asked to be driven to Astoria. I learned during the trip that she had come home to find her husband in bed with another woman, and that I was driving her to her mother’s. That was a MOMENT for her, an incident for me.

Sometimes you know a MOMENT when it happens, other times become MOMENTs only in retrospect. In my case, that would be the first time I met my cutie-pie well over forty years at an NYU party.

Yesterday I had a new MOMENT, once I instantly knew to be  a life-altering event, one I would have to live with going forward.

We’ve been having trouble with our internet connection for several days now, and yesterday we lost all connectivity. Even directly plugging a computer into the cable modem didn’t work.

My wife was of course well aware of the problem. She acquired an iPhone a few weeks ago, and has made great progress learning how to use it, while I have been left behind with my five-year old plain cellphone.

With her success has come new confidence, as  I learned last night soon after returning home.

As I entered our apartment I went to seek her out to say hello. I found her in our TV room, surrounded by a cable modem, her computer, lots of wires and power cords, and two routers.

(I had purchased a new WRT54GL to replace our dinky router provided by the cable company in the hopes that would fix the problem. When that didn’t work I got a D-Link DIR-655, a router highly recommended by fellow Newegg customers.)

I saw she was on her iPhone. She turned to me and said, “I’m on the phone with D-Link.”


I instantly knew this was A MOMENT.

In a single sentence my wife had left behind her self-confessed decades as a technological illiterate, and boldly ventured into the morass that is contemporary computer technology.

Not only was she fending on her own, she was dealing with two of the toughest adversaries in the technology industry today: cable companies and router manufacturers.

I knew my days as the “tech guru” in our household were over.

Dave, Caltech grad, PhD in computer science, geek and ace programmer, would now have a collaborator as the IT guru, a new role that would perhaps leads to a new kind of togetherness, or more likely put new strains on our relationship.

Whatever would come, I knew this was A MOMENT.

As it happens, our collaboration may be short lived. When I returned to the TV room a half hour later, she said the D-LINK support person – whose English had made evident that my wife had been talking to someone on the other far sid of the world -— was gone. The phone had gone dead.

I then looked to see what progress had been made. I noticed all the lights were off. The power cords for the cable modem and both routers had been removed. The cable coming out of the cable modem was by itself, unconnected to a device at the other end.

She said the support person had told her to unplug everything, but had never told her what to do next…

I’ll keep you posted.

Then again, you may hear from her first. She might start her own blog.

IBM Research -1, Google +1

I linked in with a former colleague from IBM Research yesterday. I mentioned in my invite that I still use Lugaru Software’s Epsilon editor. He recommended it to me over 25 years ago, and it’s been my everyday editor ever since.

Here is his reply:


Long time… It looks like you got caught up in the same “get rid of the old guys” RA that I did; what a pisser. I was very lucky and fortunate to land the job at Google, which more and more is becoming a landing spot for refugees from Research.

After many years, I finally gave up on Epsilon and switched [back?] to Emacs. There’s a very good Windoze ‘port at and, of course, it’s free although I should probably toss some money in their tip box in lieu of payments to Lugaru.

Take care, and good luck!

I had the good fortune to be associated with three great institutions: Caltech, NYU’s Courant Institute, and IBM Research.

Caltech and Courant still flourish, but IBM Research will never again approach what it once was.

A Colleague’s response on Feynman and the Higgs Boson

The fellow alum who was mentioned in my previous post, just replied as follows. As I recall, he was a Physics major (mine was Math):


I offer no comment about Feynman and the Higgs boson. However, permit me to note that either of the 2 last links in my signature (immediately below) points to work that provides a technique for cataloging types of elementary particles. There is a place (4w5) in the catalog for Higgs-like particles. The catalog includes categories for all known elementary-force-mediating bosons, a possible decomposition of the strong interaction, and more.

To the extent you are interested, perhaps you will read “Physics 642b.” It is written so that someone with understanding of logarithms and exponentials can (hopefully) learn much of what’s in the book. Permit me to attach two extracts from the book. The first extract makes two references to Feynman.

Here are the cited links:

  • Pages

  • July 2012
    M T W T F S S
    « Jun   Aug »
  • RSS The Wayward Word Press

  • Recent Comments

    russurquhart1 on SPITBOL for OSX is now av…
    dave porter on On being the maintainer, sole…
    daveshields on On being the maintainer, sole…
    Paul Tallett on On being the maintainer, sole…
    mrrdev on On being the maintainer, sole…
  • Archives

  • Blog Stats

  • Top Posts

  • Top Rated

  • Recent Posts

  • Archives

  • Top Rated