On Monday 18 April 2005 8:39 am, Jordan Crouse wrote:
> [ open vs closed device/appliance models]
>
> From a software point of view, the latter is usually controlled by a
> operating environment (usually GUI based), that is developed by the
> manufacturer and generally not hacked by the end user (most don't even
> have terminals). And of course, Linux on an open system is usually
> installed and hand tuned by the end user working closely with the
> command line.
>
> So when it comes to a closed system, then I don't see any problem with
> asking the userspace to configure everything about the policy, because
> it gives the operating environment developer the most control over the
> final device.
There's product positioning ("marketing") involved here too. Consumer
electronics models have traditionally been pretty "closed". Putting
aside (temporarily) the issue that such models don't necessarily serve
the customers as well as they serve the manufacturers, it's also clear
that "open" systems are better for non-appliance/throwaway models.
They support add-on products and multi-vendor "eco"systems, where you
can get new features by add-ons rather than (expensive) replacements.
>From the customer point of view, the attraction of "closed" is limited.
It can be a huge win in terms of ease-of-use to not _need_ to configure
things, and know "this is how you do it". Turn off brain, use product;
throw it away rather than repairing/upgrading.
I don't see major vendors wanting to move away from "closed" models
at the lower end, or in fact whereever they have the power to dictate
customer "preferences". (The latter case is also known as a "market
failure", except by radical corporatists...) But for higher end products,
or when customers truly have (or need!!) choices, then "open" is more
usually the answer.
- Dave
