HP Buys Palm for the slate market runing JS Apps

Company acquisitions are viewed as potential for the new company. "By acquiring this product the new company can expand into this market of the old company." More often, the acquiring company places value in old company as a defensive move. They don't want to be outflanked in the changing market place.

The world of mobile devices has changed dramatically in the past 12 months, but people for the most part are just getting use to what it was like 12 months ago. Example, everyone thinks App Stores are it.

First big change: App Stores are old school. Native apps are old school. The great new apps will be not be native apps written in Java or Objective-Whatever. They will be HTML5, CSS and JavaScript apps, hereafter called JS Apps. Proof is the NPR app written for iPad using SproutCore as shown at JSConf. The world has changed.

Second, big change: all major phone platforms can run these JS Apps. Blackberry is just getting caught up with the rest of the market on this. So I can now write an JS App and have it run on all phones: iPhone, Android, Palm and Blackberry. Phones are a commodity for the replacement cycle, though consumers don't know that yet.

Third big change: iPad introduced a new form factor. In part, a larger screen and touch area. This is a big deal, maybe. Market may or may not be huge. May or may not kill the laptop. It is a big deal just because it introduces uncertainty into the laptop market.

Now what is HP to do? The laptop market is being nibbled away by mobile phones or maybe being killed. Things that you only use to be able to do on the road with a laptop can now be done on your phone. You still have customers (and a brand) that depend on your products and you have a product gap that maybe huge. You acquire to fill that gap.

But wait, do your customers realize that products are changing (see above)? Not yet. But you'll be ready for them. Immediately, HP can tell customers we sell phones too. Buying number four in the market never works (see GE and Jack Welch). What was HP thinking?

Go back to third big change: new form factor. The large screens are a field HP knows well - take the keyboard off that laptop and you have a slate. How do you enter this new market? How do you become a leader? Do you take the Microsoft operating system, whatever the name is, and compete with Apple that way? Are you crazy? Too late, too old school. Microsoft has not gotten this right in 20 years. Microsoft is no help this time.

What HP does is work with the trend that mobile devices are becoming a commodity. HP knows that business. They build a slate that runs the JS Apps that also run on the iPhone, the iPad. It also runs the JS Apps written for Android and the Blackberry. Palm has an excellent development platform and team for JS Apps.

So HP buys Palm. They slap the Palm (Pilot) name on the new slate that runs these JS Apps. They are instantly number two in the new market where the App Store advantage is losing marketing power.

And besides, Palm is a better name than tongue twister iPad (or was that iPod). And look at what an old brand name (AT&T) did for Cingular. Brand names are important.

HP bought Palm not because of the phone market, but to hedge their bets in the maybe emerging market of the Palm slate. I can not wait to buy one.

This blog has moved

This blog is now located at http://blog.abcedmindedness.com/. You will be automatically redirected in 30 seconds, or you may click here. For feed subscribers, please update your feed subscriptions to http://blog.abcedmindedness.com/feeds/posts/default.

This blog has moved

This blog is now located at __FTP_MIGRATION_NEW_URL__. You will be automatically redirected in 30 seconds, or you may click here. For feed subscribers, please update your feed subscriptions to __FTP_MIGRATION_FEED_URL__.

ToDo After jsconf

jsconf was even better this year than last. A good part of that is because JavaScript and the JavaScript industry is better than last year. Missed most of the Track B talks and I hope to get caught up by watching videos. But most of my spare time may be taken up by the ToDos I wrote myself during the talks. Thought I'd share those.

1. node.js Wow - it has simply changed everything. Even if the API is constantly changing, I've got to get it installed and start using it. Needs screencasts.
2. (fab) - Mindblowing - fab:: more twitter than blogging. Just a completely new way of thinking of things and I have to try it. Also, it shows the impact of node.
3. Google Chrome Framework - Had not thought about it enough until jsconf. This will be so important to my work project. But everyone should add the meta tag to their JS pages. I have to install it at work asap and on a few other desktops.
4. yayQuery - Been following on tweeter, now I've got to listen to the podcasts. Clearly the next generation of javascript and funny.
5. Raphael - Years ago I wanted a visual, historical, problem solving site base on timelines (timeography.com). Now this is the js library to make it happen. Usable for for ANY type of vector graphics and I can not wait to push it. Reminds me of RIP for BBSs.
6. Progressive Enhancements - Jenn made the most convincing case of any presentation. I will be reading up.
7. Interface Builders - Ares and Greenhouse demos were good. Of course there is the Mac tool. I need to more take time and look at all of these -- another skill I need.
8. SproutCore - More than a year ago I was a real fan of SproutCore. I had previously argued at a Ruby meetup that MVC was broken in Rails because of the mix of data with code in the view and that the server should only produce JSON. Now that SproutCore is at 1.0 and gives me MVC on the client - will time allow a deep try? Looks so good too.
9. CVC - Client View Controller by Kyle Simpson pushes the same anti-MVC argument that I was making but puts the same JavaScript on the client and server. Again an incluence of node. Love the concept and certain that is is how the future will go, but it looks like handlebar.js and bikechain.js need to be more battle tested. Have to test to tell
10. Couchdb - The talk was on evently, but it is really Couchdb that stills interests me. Two tier solution with JavaScript and JSON. Think this will be the solution for one current project. jquery.couch.js here I come.
11. xui - prior to jsconf I went to phonegap training and heard about xui again. It would be great if jqtouch could be build on xui.
12. yql - definitely in my toolbox now

Other sessions were also great and I learned lots. For example, Facebook really showed the importance of refactoring in the browser platform. And see previous post on Socratic. And who can forget Gordon. The above are my ToDo list and possible suggestions for your exploration.

Socratic and Verbalization: Documenting on both sides

Francisco Tolmasky gave a talk at #jsconf on Socratic: Documentation Done Right. He asked for feedback and he got me thinking about the problem that coders documentation does not even help them when they go back to it. Ever have that happen with your documentation? Go back to your source comments three months later and they don't make much sense?
The process of coding involves variable and method names which are suppose to be meaningful. A convention has evolved where methods should be verbs because they do something and variables are nouns. Roughly.
So I suggested to Francisco that perhaps Socratic could use Verbalization to verify that methods are verbs. Think of Verbalization as a spell check of only verbs. Maybe it could check that "is" methods are boolean and perhaps more. I suppose the Nounization could be done on variables.
One theme at JSCONF is running JavaScript on client and the server. For example, same validation method on both. This got me thinking about the documentation divide. So why not run Verbalization on both Socratic and Textmate or your IDE. As you build out your code check that your method names are verbs. And this gets you a glossary? So a common plug system for both Socratic and IDEs would be good.
Just a thought or two with a lot more to think about.

Ed Roberts Passed Away

A true pioneer of the personal computer, Ed Roberts, passed away yesterday. Bill Gates and Paul Allen released a statement about the creator of the MITS Altair.

I bought one of the first Altair computers, soldered it together and after several tries got it working. Entered many programs using the front panel switches and later built my own keyboard. As soon as it was available I ordered the computer language BASIC on cassette from an unknown company in Albuquerque, NM, called MicroSoft.

Many happy hours were spent at my Altair and it became the platform for my first business venture: CableGames. Though not successful, it lead me into the retail software business and starting the first software store in the world in 1979. That was my career for 15 years.

The world and my life would not been the same without Ed Roberts. I still own my Altair - my first computer.

Yes We Can, Hell No You Can't, Yes We Can

Private GIT with Dropbox

This is too cool.

When I'm 58 and in the chart

Survey of lifestyles for 57 and above.

Why is technology important?

Dave Winer posted one answer to "Why is technology important?". It is an important question. Technology is a human artifact like media, innovations, language, processes, tools, clothing and any other "extensions of the physical human body - or the mind." So I will answer the question: "Why are artifacts important?" Artifacts are important because they impact our culture, our way of life. They have four effects: enhance, obsolesces, retrieves and reverses as described in McLuhan's Laws of Media. For example, automobiles enhance our privacy and travel, obsolesces horse and buggy, retrieves quests and reverses into traffic jams. You may have a different perception which is another reason why it is important to study technology and other artifacts. You can use this model to study any artifact and thus our culture.