Yes, I know. There are so many much more expensive technically incompetent products I could be writing about right now – in operating systems, networking products, switches, routers, you name it. So why would I nominate the PC CHIPs X-EYE PC Camera (USB 1.1) for “worst product of the year”? Perhaps because it was such a great big lie that it could ever work that even if I was given it for nothing it would still cost too much.
First, it claimed to be 100k pixel resolution (352 (h) x288 (v) max resolution, frame rate – 30 fps at CIF (352×288), color 16.8 million true color (24-bit), software – BMP/AVI/ TWAIN). All you need is a pentium (200 MHz), any Windows system / 32MB ram / 12MB disk. All for $15.99! Seems like a too good to be true deal, and it is.
This column is absolutely right about “clutter” on the Internet inhibiting effectiveness. And Cory Treffiletti is right in stating no one cleans up the “old methods” when introducing new ones. I suppose we all have that problem.
But when marketing fails, technology sails. The success of firefox is 1) security (e.g. block tracking), and 2) no pop ups (no ad clutter). Whenever I deal with a “creative” marketing group that thinks the world is one big contextless contentless commercial, I always see a failure in the making.
As anyone serious in this biz knows, “it’s the content, stupid”.
My latest Byte article is now online. In The Year Ahead, I predict 2005 will bring us more spam, less security, and maybe some shake-ups in search—but each of these fields holds opportunity for technical innovation. I hope you enjoy it.
The Vintage Computer Faire was held last weekend at the Computer History Museum in Mountain View last weekend. Sellam Ismail, VCF Coordinator and vintage computer collector, was kind enough to send me a couple of passes. Unlike the cozy NASA-Ames location of several years ago, the Vintage Computer Faire, typically home of games, small computers like the Amiga, and the like, has begun to nicely complement the “Big Brothers” collection of DEC, IBM, and other gargantuans in the museum’s permanent collection. What better place to talk about the good old days but in a place surrounded by a VCF buff’s beloved machines.
Last year we did a presentation at VCF 2003 entitled Before 386BSD: The Symmetric 375 & Berkeley Unix (see the mention in Talk About Legacy Machines). Symmetric Computer Systems, a venture-funded company founded in 1982 by William Jolitz, was a contender in the hot race to produce a personal BSD Unix system. The Symmetric 375 was the first system out the door with hardware floating point and virtual memory, beating Sun by years. It was the first system with open source supplied, integrated, and tested, from EMACS to SPICE for use in scientific and engineering work. And it was the first to ship systems with all software fully installed and tested, ready for use immediately. William and Lynne Jolitz discussed the design and development of the 375 computer and its influence on 386BSD – the first open source BSD system for the X86 released a decade later. That was a fun talk!
The year before that, when the VCF was still at NASA-Ames, we put together a poster entitled Symmetric Computer Systems – The Story of a Systems Startup. And that was a lot of fun, let me tell you. Ever try to get an all-wirewrap handcrafted system running? We did…
For those who would enjoy it, Byte Online presents The Problems of Personalization in the Features columns. Online retailers are crowding onto the “personalization” bandwagon—with humorous and occasionally insulting results. Join me as I talk about Amazon, Wine.com, and others as they attempt to solve The Problems of Personalization.
Martin LaMonica wrote an interesting piece in Cnet lamenting the lack of “simplicity” in web services today. According to the article “Tim Bray, co-inventor of XML and director of Web technologies at Sun Microsystems, said recently that Web services standards have become ‘bloated, opaque and insanely complex.'”. I think Bray is being far too kind.
One the the criticisms we had with the Unix operating system kernel (BSD or System V – it didn’t matter which) while creating 386BSD was the continual problem of managing a “bloated kernel” into which everyone wanted to throw their special cool thing whether it belonged there or not. When we introduced modularity in 386BSD Release 1.0 however, the reduction in complexity was not easily visualized by traditional kernel programmers used to a monolithic design, and also relegating them to a piece of the pie instead of the entire pie seemed to a few more vocal critics as “demeaning”. Web services is facing the same bias, only this time from companies anxious to have their particular widget inscribed in the annals of orthodoxy even if they are so odd that they actually belong as a special case module.
So where’s the simplicity in web services? We’ll get it when we get out of low-level design and understand the architecture better (see William F. Jolitz’s article Web Services and DataCenter Environments in the April 2003 edition of Dr. Dobbs Journal article for more information). The key is architecture in design first. This is the only way you get reliability, scalability, and security from the get-go.
Unlike kernel design, web services don’t even have an established user base yet, while people have made use of ad hoc Internet solutions using databases, scripts, and HTML / XML successfully. So perhaps, like OSI could not displace TCP/IP, web services will also “eat themselves into the grave” before they ever achieve acceptance.
Dennis Rockstroh of ActionLine in the Merc attempted to handle the frustration of a Sony Vaio user recently. Turns out the poor man continually had the power just blit out on him while working on his laptop. Back and forth to the factory it went, never seeming to get any better. Dennis helped the gentleman get a replacement laptop from the factory, but no one seemed to understand why such a problem was occurring and why it required a complete replacement to rectify. Sony didn’t wish to discuss it, and the frustrated user couldn’t figure it out other than noticing that wiggling the power connector sometimes worked.
How do I know this? Because I bought a Vaio PCG-FX-310 for my husband a few years back, and soon after acquiring it, the power connector began to fail. But since I’ve been putting together systems since the days of Symmetric Computer Systems, plus all that work on 386BSD and X86 systems from lunchboxes to desktops to laptops, we didn’t just sit around griping about the problem – we tried to figure out exactly why this happens – both as a good little example of the importance of design in a consumer product, and as an illustration of the difference between American and Japanese audiences.
Dropped by Miro Samek’s talk “Hierarchical State Machines: a Fundamentally Important Way of Software Design” at PARC last week, and still thinking about it. While the title is a bit over-the-top, some of the ideas such as a “quantum language” fit quite nicely in an RTOS. Of course, it’s architecture, architecture, architecture.
Mr. Samek himself sees the “framework” as applicable to many areas, such as real-time embedded systems, GUIs, or networking servers. He also is working on a realtime preemptive kernel which he says he will release soon. Why? As he put it himself “Obviously, what I’m doing is cottage-industry, but that’s all I can do alone.” Sounds like a good enough reason – just to try and see if it flies. That’s what exploration is all about.