
	Where results make sense

Topic: Write once, run anywhere

	History of Java programming language \| www.freejavaguide.com
		Although it is indeed possible to write programs for the Java platform that behave consistently across many host platforms, the large number of available platforms with small errors or inconsistencies led some to parody Sun's "Write once, run anywhere" slogan as "Write once, debug everywhere".
		The println(String) method is called to write the "Hello, world!" string to the response and then the close() method is called to close the print writer, which causes the data that has been written to the stream to be returned to the client.
		Note that once the frame is displayed, exiting the main method does not cause the program to terminate because the AWT event dispatching thread remains active until all of the Swing top-level windows have been disposed.
	www.freejavaguide.com /history.html (2571 words)

	Write once, run anywhere - Wikipedia, the free encyclopedia
		"Write once, run anywhere" (WORA), or sometimes also Write once, run everywhere (WORE), is a slogan created by Sun Microsystems to illustrate the cross-platform benefits of the Java language.
		For example, this means a programmer can develop code on a PC and can expect it to run on Java enabled cell phones, as well as on routers and mainframes equipped with Java, without any adjustments.
		Hence the expression 'Write once, run anywhere.' This is intended to save software developers the effort of writing a different version of their software for each platform or operating system they intend to deploy on.
	en.wikipedia.org /wiki/Write_once,_run_anywhere (314 words)

	Write once, compile anywhere - Wikipedia, the free encyclopedia
		Write once, compile anywhere (WOCA) means writing software that compiles and is thus useable on all platforms.
		As difference to Write once, run anywhere, care of compatibility is taken at code level, instead of binary level compatibility.
		WOCA is the philosophy that cross-platform applications in languages like Ada or C take.
	en.wikipedia.org /wiki/Write_once,_compile_anywhere (111 words)

	Java 'Writes Once,' But Does it 'Run Anywhere' Yet? Thousands of Developers Respond to JavaWorld Internet Poll
		Thousands responded to the survey, revealing (in very certain terms) just how satisfied they are with Java's current "write once, run anywhere" capabilities, and how important cross-platform portability is to their work as professional developers.
		"write once, run anywhere" is absolutely key to enhancing platform choice and competition.
		While I don't feel that Java is currently "write once, run anywhere," I do feel that it's on the right track and will come to that point in the near future.
	www.prnewswire.com /cgi-bin/stories.pl?ACCT=104&STORY=/www/story/12-8-97/373674&EDATE= (842 words)

	WAP analysis : opinion : uidesign.net
		If it was 15,000 people in a global corporate running over a WAN then it was an engineering and logistical problem which carried huge risk and often saw failure.
		The truth is that "write once, run anywhere" just doesn't work for human computer interaction across different screen sizes.
		"Write once, run on a single form factor device" is the rule.
	www.uidesign.net /2000/opinion/wapknuckles.html (2017 words)

	VM enables "write-once, run anywhere" Linux apps
		The concept recalls Java, which has long promised "write once, run anywhere" compatibility.
		As with Java, Lina users will first install a VM specific to their platform, after which they can run binaries compiled not for their particular OS, but for the VM, which aims to hide OS-specific characteristics from the application.
		"One of the reasons Java ran into problems [delivering the "write once, run anywhere" promise] was because of cracks in the API," he adds, noting that they also didn't use an open source license.
	www.linuxdevices.com /news/NS6279947776.html (1146 words)

	Print Article: Write once - run anywhere
		These can be quite convenient if you have to run a number of queries where the only difference is in the data that is being passed to the database while the structure of the query remains the same.
		The first two are used when you want to write a LOB into the database.
		Once MDB has caught up with PEAR DB in terms of drivers it is likely to become the standard database abstraction layer in the PEAR framework.
	www.phpmag.net /itr/online_artikel/psecom,_psframe,,linkobject,print_,nocontainer,1_,id,283,nodeid,114.html (4271 words)

	Application Development Trends - Not another Unix?
		What happened to Java's virtue of "Write once, run anywhere?" About a year ago, it seemed inevitable that Java would soon join HTML as "the next big thing." It would deliver the long-awaited intelligence and versatility of fourth-generation languages to the Web, transforming it into a true enterprise application environment.
		Instead of "Write once, run anywhere," the IT world is now wondering which flavor of Java to write and where.
		Yes, there were technical hurdles to the "Write once, run anywhere" goal, such as slow performance of JVMs compared to native compilers, but nothing that a little clever technology and diplomacy couldn't have settled.
	www.adtmag.com /print.aspx?id=4127 (746 words)

	TWiki . Javapedia . JavaDeployment
		There is a lot of hype about the "Write once, run anywhere" motto Sun shouts about Java.
		What is not commonly discussed is that by adding the indirection layer of the JVM, much of the difficulty of writing code in other languages is transferred to deployment in Java.
		"Write once" is hardly compelling since that has existed for many years prior to Java.
	wiki.java.net /bin/view/Javapedia/JavaDeployment (469 words)

	Feature Article - Java is Making the Integrated Supply Chain Come True - 12/97
		Once in your computer, the applets run in the JVM—that computer within your computer—that came with the Web browser you use.
		Before this code runs, a verifier mathematically ensures against bad things from happening, such as the "worm" that brought part of the Internet to a standstill a few years ago.
		Given that, Ariba's ORM is a networked application with Java applications running on thin-client workstations throughout the enterprise and Java adapters to embrace, that is integrate, existing enterprise resource planning and human resource applications, databases, messaging systems, and so on.
	www.autofieldguide.com /articles/129707.html (1973 words)

	Between the Lines mobile edition (Site not responding. Last check: 2007-11-07)
		As I described in that blog, NetBeans is an integrated development environment (one that embodies the write once run anywhere religion of Java) that's currently losing in an important popularity war against its rival IDE Eclipse.
		The question is, once you step outside the write once run anywhere sanctuary — even ever so slightly — could the situation spiral out of control from there to the point that you really are no better off than writing dedicated applications?
		But once you throw the equivalent of a second runtime into the equation, many more of the write-once, run-anywhere bets, even within a single platform like Windows, could be off.
	blogs.zdnet.com /BTL/wp-mobile.php?p=1571&more=1 (797 words)

	'Write once, run anywhere' not working for phones (Site not responding. Last check: 2007-11-07)
		Though that's understandable, since they have to deal with the immediate needs of the market, their actions have played a major role in sullying the "write once, run anywhere" promise of MIDP, say Sun executives and developers of cell phone software.
		That means that the extra costs and development time associated with creating multiple versions of the same software find their way into nearly every corner of the cell phone industry, from the price of handsets to the price for downloading a ring tone.
		Writing multiple versions of software can mean adding months of additional work on a program.
	www.zdnetindia.com /print.html?iElementId=125542 (871 words)

	Linux Aviation HOWTO: Java based Software
		The write once, run anywhere feature of Java now makes it very easy for the developers of application software to let their users decide which operating system they will run the application on.
		When running Java applications, it is not uncommon for the interpreter to experience difficulty locating the byte code for the classes it needs.
		Once you get things figured out, you may want to write a small shell script to simplify the process of starting the application.
	www.ibiblio.org /fplan/Aviation-HOWTO/Aviation-HOWTO-3.html (1179 words)

	TechOnLine - Write Once, Then What?
		It was intended to be a language by which applications could run on any machine without changes.
		The rallying cry "write once, run anywhere" fired the imagination of developers worldwide.
		Applications could come through the network, run on the machines, then be discarded from local memory when not needed.
	www.techonline.com /community/tech_group/embedded/feature_article/8618 (845 words)

	Object Computing, Inc. - Java News Brief - May 2006
		The team attempted to come as close as possible to meeting Java's "write once, run anywhere" mantra without compromising the capabilities required by real-time systems.
		Upon reaching 0, the scope is deleted and finalization code is run on each associated object.
		Once a transfer of control is triggered from a method, control does not come back to that method.
	www.ociweb.com /jnb/jnbMay2006.html (2801 words)

	How to Write Comments
		Often it is a matter of negotiation to determine who writes which parts of the documentation, based on knowledge, time, resources, interest, API complexity, and on the state of the implementation itself.
		Then a writer can proceed to write an API specification only if they either know the intent of the designer (either through design meetings or through a separately-written design specification) or have ready access to the designer with their questions.
		This helps engineers write code to be "write once, run anywhere." * As much as possible, write doc comments as an implementation-independent API specification.
	www2.hawaii.edu /~rayo/ICS211/COMMENTTIPS.html (7574 words)

	Dr CE
		You'll recall that Java's main promise was "write once, run anywhere" technology that would allow developers to do just that write one program and have it run successfully on any machine.
		Currently, when developers write programs for Windows CE, they have to make a separate version of their program for each of the CPUs that might be powering a Windows CE device.
		Essentially, at this level CEF is a "write once, run on any CE device" technology.
	www.pocketpcmag.com /_archives/Sep99/DrCE.htm?404=was (793 words)

	K Java Virtual Machine - JVM, J2ME, small, embedded, compact
		The problem with the "write once, run anywhere" mantra is that it doesn't acknowledge the reality of resource constraints or offer would-be Java programmers any other option.
		It is certainly much more likely that the owner of a cell phone from one manufacturer would want to run a Java utility, application, or game written for another brand of cell phone, than that the owner of a logic analyzer would want to run Java code originally written for use on a microwave oven.
		The only platform-dependent functions you'll write to port KVM are concerned with allocating big chunks of memory for heap expansion, deallocating the same, returning the current system time, and handling user interface issues.
	www.netrino.com /Articles/SmallerJava (3509 words)

	Write once, run everywhere -- no kidding \| InfoWorld \| Review \| 2005-04-11 \| By Tom Yager
		Write once, run everywhere -- no kidding
		The beauty is, once again, the ability to put the businessman in the driver’s seat.
		The myth of “write once, run anywhere” has been turned on its head.
	www.infoworld.com /article/05/04/11/15TCoracle_1.html (2181 words)

	Java on mobiles: Write once, run... once?: ZDNet Australia: News: Communications (Site not responding. Last check: 2007-11-07)
		The Java programming language was built on the premise that a program written in it can run on any platform that has a Java Virtual Machine.
		Part of the problem, he added, is that Sun, which created Java and controls the language through the Java Community Process, is not in a position to enforce hardware standards with handset makers.
		Write once run anywhere just doesn't happen." A developer who wants to write a game for every device would have to do 24 versions just for the different screen sizes, he noted.
	www.zdnet.com.au /news/communications/print.htm?TYPE=story&AT=20267918-2000061791t-10000003c (947 words)

	``Write Once, Run Anywhere'' Is a Promise (Site not responding. Last check: 2007-11-07)
		Specifically, that they should be able to work together to do as their users want, regardless of who makes them or the software they run.
		A large degree of the interest in Java is because Sun has presented it as a ``Write Once, Run Anywhere'' technology.
		Programmers who do not recognize these undocumented changes can build their applications expecting them to run anywhere that Java can be found, only to discover that their code works only on Microsoft's own Virtual Machine, which is only available on Microsoft's own operating systems.
	interhack.net /people/cmcurtin/rants/write-once-run-anywhere/node5.html (337 words)

	'Write once, run anywhere' not working for phones \| CNET News.com (Site not responding. Last check: 2007-11-07)
		Sun's Java for cell phones was supposed to let developers write a single program that could run on any handset.
		It's becoming clear to Sun engineers that the ultimate goal of "write once, run anywhere" may never be fully realized because the cell phone market is simply too diverse.
		The latest attempt involves the Java Verified program, which was created several months ago to certify cell phone software and ensure that it runs on different companies' phones.
	news.com.com /Write+once,+run+anywhere+not+.../2100-1037_3-5788766.html (1086 words)

	USENIX ;login: - java
		We discussed writing to Java 1.1 to be used in Netscape 4, which was also due out "real soon now," but decided it would be difficult to develop for a platform that did not yet exist.
		Java is much more portable than C. Assuming that you write "pure Java," the core features of the language really do live up to the promise of "Write once, run anywhere." I've never seen any instance of basic functionality that is different from platform to platform.
		With the current set of runtime environments, writing portable Java is very much the same as writing portable code in other languages: there are lots of little annoying things that differ from platform to platform.
	www.usenix.org /publications/java/usingjava10.html (1932 words)

	Reference.com/Encyclopedia/Write once, run anywhere
		"Write once, run anywhere" (WORA) is a slogan created by Sun Microsystems to illustrate the cross-platform benefits of the Java language.
		The catch is that JVMs are written for a wide variety of different operating systems, such as Windows, Linux, Solaris NetWare, HP-UX, and MacOS.
		However, many Java developers joke that "Write once, run anywhere" is actually a euphemism for "Write once, test everywhere".
	www.reference.com /browse/wiki/Write_once,_run_anywhere (295 words)

	Pocket PC Thoughts :: Print Version
		Given both the hardware standardization of Pocket PC and Smarthpone and the fact that the core components of the.NET Compact Framework is designed to be hardware and operating system independent, Microsoft has positioned itself well to compete with the Java camp.
		Some Java developers have written to me saying that, based on their experience, Java's "write once, run anywhere" promise is a pipe dream.
		In an effort to write one set of code that can be deployed anywhere (or almost anywhere), they can study all the devices that they want their J2ME-based applications to run on in order to find a lowest common denominator to target.
	www.pocketpcthoughts.com /print.php?action=expand,7762:dont_paginate,1 (381 words)

	Rich Green
		We're empowering distributors of free Java implementations to be part of the "Write Once, Run Anywhere" promise, while fulfilling all of their obligations under the GPL.
		Anyone who flunked their first driver's exam probably wished then that they could change the test to conform to their mistakes, but the rest of us on the road are all glad that is impossible.
		But because the Apache code is not governed by the GPL, and does not require code sharing by any entity using or modifying Harmony, the terms of this license are the same terms under which Sun licenses the JCK to commercial entities that build their own independent implementations of the Java SE platform.
	blogs.sun.com /richgreen (4646 words)

Try your search on: Qwika (all wikis)