Talk:Write once, run anywhere/Archives/2012
 | This is an archive of past discussions about Write once, run anywhere. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Need a critique section
lots say it's a lie
- Actually, even on Java itself, lots depends on the version of the Java platform--VictorAnyakin 07:18, 4 July 2006 (UTC)
POV
I think the link section, whose only working link point to a single project. I acctuly thought that this was some guys way of getting his project known, as it has little to do with the article (there is no section that JAVA is not WORA, and the links are not that java isn't WORA, jsut that it doens't supply functions that would not make it a WORA). For those reasons I have deleted the External Links section.--Jimktrains 18:27, 24 July 2006 (UTC)
Compile once, run anywhere
I hereby request a move to Compile once, run anywhere. It's used much more than "Write once, run anywhere". And you *do* compile once and the run it anywhere, at least in Java, at least in theory. And I'm sure the "normal" way is to write your code, compile it and then run it. Writing and compiling is done only once, on your (the devs) pc. User can run the app wherever they want, can run it anywhere. Sorry for my poor english, it's already late... --89.61.73.40 19:11, 7 March 2007 (UTC)
Write once, debug everywhere
This is definitely a common saying among anybody programming Java. It's a bit cynical but the first place I heard it was my programming professor. I've heard it multiple times since then. You could find a more reliable source but really there's no need for the citation tag — Lunarbunny (talk) 09:15, 8 December 2007 (UTC)
Paradigm?
This seems more like a (desirable) property of some languages, than a programming paradigm. Any thoughts? Thebigclaw (talk) 04:12, 13 April 2008 (UTC)