First, we should not forget that the FSF has boycotted MacOS for years (a problem with copyrights on the GUI, IIRC). Second, OpenSource software is basically written by developers who will use their products, which means OpenSource software is written from developers to developers. Developers typically love to configure everything via a configuration file, love to do everything with their keyboard without repeating the same task twice (think vim/emacs). OTOH, Apple has always targetted the MacOS for end-users, who typically want to have their job done, without exactly knowing how it will be done, and without needing to read a billion of pages of documentation to find out 'how' to do it.
This means Apple has found no interest in putting a command line in MacOS, this means Apple found that the user interface should be similar between applications (from all the Inside Macintosh series of book -- the developer books which describe how the OS works --, the only book which has been translated in nearly as many countries as Apple has developers in is "Interface Guidelines", which teachs developers how to write a good interface, how to spell the item, where to place buttons in dialogs, aso).
All that put together, quite no OpenSource developer was feeling the *need* to write OpenSource software on MacOS. Now, things may be changing with MacOS X, as the article suggest. Let's hope it will be the case, this is good for the entire community.
cwis, who ported BitchX to MacOS
Is Wap really connecting people to the "Internet"?
on
WAP Under Fire
·
· Score: 2
What I find most boring with WAP is that cellular phone companies claims that "WAP will allow customers to access the Internet". But I'm really afraid that only companies may find interest in adding some WAP contents on their site, which means WAP users will mostly be able just to surf commercial sites.
Of course, phone screens are limited in size, and only a few people would enjoy the "hi-I'm-Joe-this-is-my-first-webpage-look-the-fanc y-animated-gif-and-my-very-k3wl-@aol-ema il-address", but designing a so-called 'standard' which avoid the masses to publish on the media, and, furthermore, calling this "the Internet", is, IMHO, a mistake. This is roughly the same as when Microsoft modifies its Java implementation. No wonder the IETF is critizing the standard.
Slashdot Mirror
Furthermore: 8*8*8 = 512. 5 + 1 + 2 = 8.
<br>We're getting lucky, eh?
In France, you can use 30 seconds of a song without violating copyrights.
Now, instead of ringing, phones are also able to vibrate.
Which means users who don't want to disturb other people are already able to do so.
Doesn't that turn that feature pointless?
This means Apple has found no interest in putting a command line in MacOS, this means Apple found that the user interface should be similar between applications (from all the Inside Macintosh series of book -- the developer books which describe how the OS works --, the only book which has been translated in nearly as many countries as Apple has developers in is "Interface Guidelines", which teachs developers how to write a good interface, how to spell the item, where to place buttons in dialogs, aso).
All that put together, quite no OpenSource developer was feeling the *need* to write OpenSource software on MacOS. Now, things may be changing with MacOS X, as the article suggest. Let's hope it will be the case, this is good for the entire community.
cwis, who ported BitchX to MacOS
Of course, phone screens are limited in size, and only a few people would enjoy the "hi-I'm-Joe-this-is-my-first-webpage-look-the-fanc y-animated-gif-and-my-very-k3wl-@aol-ema il-address", but designing a so-called 'standard' which avoid the masses to publish on the media, and, furthermore, calling this "the Internet", is, IMHO, a mistake. This is roughly the same as when Microsoft modifies its Java implementation. No wonder the IETF is critizing the standard.
Maybe you are looking for http://lhd.datapower.com/?