Some Internet appliance and embedded device developers have concluded that current implementations of the Java™ specifications are either functionally incomplete for their use, too slow, too unreliable or too big. Sun™ Microsystems estimates there are more than 700,000 developers using Java technology today. While there are many documented success stories regarding the use of Java platforms for corporate or enterprise applications, there are few public illustrations of the use of Java technology for Internet appliance and embedded device development. In order to look at the current situation more objectively, we will review "Java technology" from two perspectives: 1) specification, and 2) implementation. As a longtime developer and provider of virtual machine technologies, Insignia Solutions believes that the current specifications for Java platforms (including Enterprise Java, PersonalJava, and EmbeddedJava) are not at fault, but rather, most current implementations, particularly for PersonalJava™ and EmbeddedJava™, are not viable for most Internet appliance and embedded devices. This article discusses alternative ways to implement Java technology to effectively address these legitimate concerns. The article begins with an introduction to Java technology that will orient readers who are new to the subject, and possibly serve as a refresher for those already acquainted with it. It will discuss the evolution of the virtual machine and then delve into alternative approaches available to implementing a Java virtual machine for small memory footprint devices. Specifically, it will address class file loading and execution, employing dynamic compilation techniques versus Just-in-Time (JIT) compilation; key issues in ensuring JVM reliability; and employing precise versus conservative garbage collection. Finally, the article will describe an implementation of a Java virtual machine that addresses many of these issues.