Re: Cross-platform, the freedom to choose any computer



toby wrote:
Peter Ammon wrote:
Otto Wyss wrote:
I think it's worth to think a little about "Cross-platform Development"
and have therefore written this paper here:

http://wyoguide.sourceforge.net/index.php?page=Cross-platform.html

See for yourself, if it's something you can use.

O. Wyss
If every program runs on every platform, what's the point in having more
than one platform?

In the real world, there are hundreds of different platforms. The more software can be made available on the wider variety of hardware, the better off end users are.

I am using Mozilla Thunderbird, a highly portable program, to type this message. Mozilla Thunderbird appears to do its own contextual menu handling - the typeface and font size of its menu items is different from other applications, the menu vanishes instead of fading out, the shadow is drawn differently, and the cursor remains an I-beam instead of becoming the arrow when the menu is opened. The effect is unpleasant and visually jarring. These bugs exist because of its portable nature - because it attempts to do menu handling the same way on multiple OSes.


There's a tradeoff between making your software portable and making it a "good citizen" on the platforms you target. The OP advocates making every piece of software run on every OS; that's a recipe for terrible software on any particular OS.

This is the FSF's quite rational position.

Put another way - if you don't code to take advantage of the features
and obey the human interface standards of a particular platform, your
program will be inferior (on that platform) to one that does.

I guess we must first exclude the tens of thousands of portable command line tools and libraries on any UNIX system from your argument.

Not at all, it's just as applicable. Example: the venerable BSD cp command knows nothing of multiple file forks on Mac OS X (a flavor of Unix, note). Copying a multi-forked file with cp will corrupt it. Apple eventually fixed this bug by adding OS X specific code to cp, which rendered it less portable.


-Peter

--
Pull out a splinter to reply.
.



Relevant Pages

  • Re: Authentication failed suddenly
    ... >> off on such a platform, ... the developers don't consider it a fundamental part of the distribution. ... >The bugs are platform compatibility bugs. ... bugs and report them - rather than rambling in public fora ...
    (comp.security.ssh)
  • Re: Writing portable applications
    ... > previously stated, Sturgeon's law applies to the web, so chances are ... > The only difference is that the user of Platform 54 has a chance to ... it may not work because that platforms bugs are ... >> vendor refuses to fix a bug and ask THEM to ask that vendor. ...
    (comp.unix.programmer)
  • Re: [RFC, Announce] Unified x86 architecture, arch/x86
    ... have a nice style that you like and think that it is cleaner. ... It's not really the same platform: one is PC hardware going back forever ... with zillions of bugs, the other is modern PC platforms which much less ... That was not the point of this patch. ...
    (Linux-Kernel)
  • Re: Writing portable applications
    ... >> interfaces. ... > But as soon as some user of platform 54 tries your website, ... it may not work because that platforms bugs are ... > tons of inter-application traffic in XML already, ...
    (comp.unix.programmer)
  • Re: SurGard MLR2000
    ... of them left that even know any of their receivers. ... But the SG-III is a platform to improve on, ... The bugs of that receiver have definately not ... Great, glad to hear others are using DNIS also, I have ran into others ...
    (alt.security.alarms)