On 5/28/07, Tels <nospam-abuse(a)bloodgate.com> wrote:
Exactly. Teach them to not write their software for
some system so that the
result is vendor-locked in into an OS, and a platform at the same time.
I've developed a few things for Windows over the years. That advice
just isn't helpful. If you develop using MS Visual Studio or Borland
Delphi, there is no trivial habit you can suddenly kick which would
make your wish come true. Windows developers don't write software that
only works on Windows out of spite. They do so because they have
access to the tools, their knowledge is of Windows (as opposed to the
often scary world of *nix) and, in many cases, 95%+ of their potential
clients are using Windows.
Make a compelling reason for people to write stuff for multiple
platforms, or make it trivially easy for them to do so, and they will.
Anyway, about AWB: it's not the solution here. AWB is a hack. Let's
get a real *client* happening, not a toolbox of different solutions to
particular problems.
Steve