Linked by Thom Holwerda on Mon 22nd Jun 2009 10:45 UTC
Permalink for comment 369616
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
More News »
Sponsored Links



Member since:
2005-08-07
Or what is a non-native browser? A browser needing a JVM or CLR to run? Or one that runs inside an emulated OS (but why would it be called a Haiku browser in the first place)?
Please do not abuse the word 'native'. It really turns off technical people. 'Native' means just that a program runs on a processor without emulation. Somehow I am pretty sure that it's not what the author means. It might mean that it has been written specifically for Haiku, or that it uses Haiku's default graphics toolkit, or that it is well integrated (file associations, etc.), or that it is 'quick and snappy' as opposed to 'slow and bloated', or that it just has a cool yellow tab at the top. The word 'native' has become a catch-all phrase here at OSnews lately and could mean anything from the above list or nothing at all. Wouldn't it be more informative to say 'dedicated', 'having a platform-specific look and feel', 'well integrated', etc.?
I know that the 'nativeness' comes from the linked article. Still it is an article in its own right on OSnews (as opposed to a simple page 2 link), so I would expect the term to be either dropped or explained.