« September 2007 | Main | November 2007 »

October 2007

October 18, 2007

Ethics, Ideology, and Pragmatism

Blogger: Joe Niski

JoeniskiofficialThe week started with this stimulating interview with Grady Booch, in which he makes a case for examining the larger implications of what we do while deftly avoiding taking a stand on any of the issues the interviewer tossed his way. He also put in a good word for Computer Professionals for Social Responsibility. After reading the interview, several events of this week seemed to fall together under the broad theme of ethics, ideology, and pragmatism in the wide world of software.

First, Eric S. Maskin shared the Nobel Prize in Economics with Roger B. Myerson and Leonid Hurwicz for their work on mechanism design theory (started by Prof. Hurwicz). In 2000, Maskin co-wrote a compelling paper on why software patents are more likely to stifle than stimulate innovation. At the risk of oversimplifying, he shows that the software companies, users, and innovation in general all benefit from the free exchange of ideas and plenty of competition. It's a quantitative argument about an issue that typically flames the ideological passions of programmers and ISVs - how refreshing!

By mid-week, the US Patent Office rejected much of Amazon's patent claim for one-click shopping. While bloggers are alternately rejoicing and compulsively analyzing the legal fine points,  it's nice to see a little common sense coming from the USPTO - even if it's the result of a challenge.

And today, Canonical released version 7.10 of Ubuntu Linux. After trying numerous versions of numerous distributions on my aging no-name laptop, I've been having a lot of fun with 7.04 - it's the first Linux I've been able to get working with multiple monitors. While Ubuntu is known for its ease of installation and use, it's also looked down upon by some Linux and open source purists for some of the tradeoffs made in the distribution. One of these is an admirably pragmatic way of providing closed-source software - a "restricted" repository that integrates with Ubuntu's software-management system, but is separate from the primary distribution. It honors the the OSS ethos, without limiting users' freedom of choice in the software they install.


Apple planning iPhone SDK for February

Blogger: Richard Monson-Haefel

Richardmonsonhaefel

Link: Apple planning iPhone SDK for February! - Engadget.

Well its about time that Apple provided an SDK for creating resident applications on the iPhone. That's my biggest gripe with the device (which I own) from a enterprise perspective is that you can't have off-line resident applications which really are a much better experience than web based applications.  Not sure about Apple's plans to require signing - I figure this is just a way to make iTunes the only source for commercial applications built on the SDK.

October 17, 2007

SOA presentation now available on parleys.com

Blogger: Anne Thomas Manes

Annethomasmanesbg

I gave a keynote speech at the BeJUG Enterprise SOA Conference in Affligem, Belgium, on October 9. The folks from BeJUG (i.e., Stephan Janssen) have been kind enough to post my speech, Making the Most of your SOA Initiative, on parleys.com.

October 16, 2007

Sentilla makes Ubiquitious Computing easy

Blogger: Richard Monson-Haefel

Richardmonsonhaefel

You may have heard of a field of computing and electronics called "Ubiquitous Computing" (a.k.a. "pervasive computing", "everware", etc.) which has always held great promise but has never taken off. Well, it’s about to and I suspect that the product being introduced as a beta by Sentilla will get things going and change the world as we know it.

Ubiquitous computing is the idea that everyday things everywhere are intelligent and networked. Is that a big deal? Why yes, because the possible applications of this type of technology are seemingly infinite and their impact will be immeasurable huge. The rise of ubiquitous computing, which thanks to Sentilla will take place sooner rather than later, is what I refer to as a Technami: A mega technology trend that fundamentally alters our world. To give you some context, other technamis include the internal combustion engine, the telephone, the computer, and the Internet.  Technamis on the rise include genetic engineering and nanotechnology. And now I can add "ubiquitous computing" to the list because, for the first time, it actually seems feasible on a grand commercial scale.

The best way to  express this is through example - more technical or architectural explanations tends to lead people away from what is most important, which is the practical applications of ubiquitous computing.

In the future automobiles will have, on average, tens of thousands of sensors arrayed throughout the vehicle. Some sensors will measure heat; others pressure, speed, force, and so on.  Your tires, pistons, seat cushions, headlights, gas filter, spark plugs, and everything else will have a built in sensors, sometimes many of them.  All these sensors will automatically network together and with programming, communicate with actuators and gages to allow your car to adjust immediately to changes in conditions and to report the smallest change to the driver or to diagnostic devices. Sensors today are about the size of a quarter and draw so little power that their small batteries last them years. If you buy new tires, your new tires will automatically join the sensory network without you having to do a thing. The same is true for any other part on your car.

Another example is a home security system. Imagine you go out to Wal-Mart and buy a bag of security sensors that can detect movement or sudden changes in velocity. You stick each sensor, the size of a quarter, on all your windows and doors and then install some software in your computer after which you Housemote have a complete home security system.  Each sensor will relay any motion or change (e.g. breaking window) to other sensors and eventually to your computer which can call the police, set off an alarm, or text message you when there is a break in.  The home security system cost you $99.00  and you installed it yourself  in the time it takes to put stickers embedded with sensors on all your windows and doors.

Imagine sensors in every item of packaged food you buy from the grocery store. Each food time, via its sensor, can connect up to your home fridge the second you put them on the shelf. Each item reports its temperature, expiration timing, and can report spoilage all of which allows the fridge to automatically adjust temperature and air flow and to alert you when something needs to be done (like take the spoiled yogurt out of the fridge).

I could go on but I'm afraid I'm selling the technology short. Not only are Sentilla sensors, which they call "Motes", able to network they are also programmable using  standard Java ME.  In fact, Sentilla plans to offer an Eclipse based IDE and frameworks so that the average Java programmer can fashion and easily deploy their own applications out of a heap of sensors.  Different Java APIs will be provided for different sensory capabilities.  This is why Sentilla's new platform is so important - it makes it possible and feasible for the average developer to create a pervasive net of sensors that use peer-to-peer communication over wireless networks to communicate, coordinate and report on just about anything. The limit to these types of systems is your imagination.   I don't know about you, but my head is exploding with ideas for commercial products.  The best part:  I will be able to eventually (after the beta is over) buy Sentilla motes, their IDE, and the frameworks I need to build anything I want. How cool is that?

Update: James Gosling just blogged about Sentilla's motes here - a little link love for the Father of Java.

October 13, 2007

BEA rebuffs Oracle's bid for $6.7 B

Blogger: Anne Thomas Manes

Annethomasmanesbg

BEA rebuffed Oracle's bid on Friday afternoon, claiming that $6.7 B "significantly undervalues" the company. Even though the bid was 25% over BEA's stock value. Of course in response to the expected bidding war, BEA's stock has surged to $18.82, up more than 38% in a single day.

Now it's up to Oracle to come back with a counter offer. Let the negotiations begin.

Although Alfred Chuang has indicated that he wants BEA to stay independent, I seriously doubt that the board and the BEA stockholders will be able to resist the offer.

As for counter offers?

Speculation has been focusing on SAP, HP, and IBM:

BEA doesn't really offer much to SAP. Because of mySAP's use of ABAP, the WebLogic and AquaLogic product families can't displace NetWeaver. BEA has a few nice bits that SAP could exploit: AquaLogic Data Services, AquaLogic Enterprise Security, the SIP server extension to WebLogic Server, and the Workshop tooling. But those bits certainly aren't worth >$7 B to SAP.

HP has repeated stated that it doesn't want to get back into the application runtime business. It's focused on management -- not runtime. I'd be surprised to see HP jump into the bidding war.

I think IBM has the most to gain from BEA -- if only to prevent Oracle from getting it. Oracle + BEA will be a much stronger force in the superplatform market than the two companies on their own, and the combination should be giving IBM night sweats.

Other possible counter offers?
- Microsoft (not likely)
- Dell or Intel (possibly -- if they were considering getting into the platform business)
- Red Hat (not likely)
- Novell (if only they could afford it -- but that combination would be doomed)
- Software AG (maybe, but it would be an awfully big bite -- especially so soon after webMethods)
- Tibco (maybe, but again -- it would be an awfully big bite)
- Sun (well, now there's an idea -- but I would hate to see it happen)

October 08, 2007

The Ultimate Smartphone

Blogger: Richard Monson-Haefel

Richardmonsonhaefel

ComputerWorld compared the iPhone, Nokia N95 and the HTC Touch in Usability test: Does iPhone match the hype?.

"Let's cut to the bottom line: In terms of usability, iPhone blew away its two competitors. Its overall score in the usability tests was 4.6 out of 5. The HTC Touch was a distant second at 3.4, and the Nokia N95 scored 3.2."

When it comes to usability the iPhone is unrivaled and that speaks volumes about simplicity and great experience design. In short, less features and great design can make a phone more usable - but don't we also want the features and ease of application development?

The Nokia N95 is one of the most feature-rich smartphones available today - but its not as easy to use (so the report says) as the iPhone. The HTC Touch sports the Windows Mobile 6 operating system which includes .NET Compact Framework making it an excellent platform for enterprise development (lots of features, great tooling, extensive integration).   

The ultimate smartphone, in my opinion, would offer the features of the Nokia N95, the operating system and application development framework of Windows Mobile 6, and the wonderful usability of the iPhone.

October 01, 2007

Roy Fielding on REST

Blogger: Anne Thomas Manes

Annethomasmanesbg

There's no one better to explain REST than the man that defined it. Roy Fielding gave a presentation recently at JAZOON 07, and the folks from BEJUG were kind enough to post a recording of the session on Parleys.com.

Roy described REST from a fairly technical perspective, and unfortunately he was a bit rushed in his presentation. (He learned at the last minute that the session was much shorter than he expected.)

I particularly like the way he summarizes the REST constraints. Plagiarizing his slide:

Uniform Interface:

  • Resources are identified by only one resource identifier mechanism
  • Access methods (actions) mean the same for all resources (universal semantics)
  • Manipulation of resources occurs through the exchange of representations
  • Actions and representations are exchanged in self-describing messages

Hypertext as the engine of state:

  • Each response contains a partial representation of server-side state
  • Some representations contain directions on how to transition to the next state
  • Each steady-state (page) embodies the current application state

I'm not quite so fond of the way he compares REST to SOA. First of all, it really isn't appropriate to compare REST and SOA. SOA is an architectural style that should be used for high-level system design, while REST is an architectural style that should be used for system implementation. (I discussed this last June in the blog entry SOA and REST operate at different levels of architecture.) And second, Roy is equating SOA with web services. Although a lot of folks use web services to implement services, that's simply an implementation decision. Any type of middleware can be used to implement services. (I discussed this topic in September in the blog entry When Technology Matters in SOA.)

Stefan Tilkov also posted an excellent discussion about the different architectural levels of REST and SOA, FAQ Entry: What's this REST vs SOA Debate About?

So when watching Roy's presentation, replace the term "SOA" with "WS-*", and the discussion will make a lot more sense.

Burton Group Podcast

Blog powered by TypePad