![]() | This is an archive of past discussions. 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. |
Archive 1 | ← | Archive 3 | Archive 4 | Archive 5 | Archive 6 | Archive 7 |
The License section of the Criticisms section refers solely to Sun's implementation of Java stating that "Java [...] cannot be included in projects [...] such as Debian". This is not true, Debian does include a Java compiler, albeit an incomplete one, in the form of GCJ.
I'm not suggesting that the problems of Sun's Java implementation and its decendands which is the predomenant one should be downplayed, merely that the distinction between the two needs to be made clear to the reader, and the article does a very poor job of informing the reader about which it is referring to at any time, using the blanket term "Java" for everything, which is ambiguous. -- Ævar Arnfjörð Bjarmason 18:59, 29 May 2006 (UTC)
This Criticisms section really has gone too far. This section needs to be stripped of what does not belong in it (roughtly, almost all the text), and present a real SYNTHESIS of common critics about Java. I don't think the "language irregularities" is in the right place too (for example, why putting in irregularities the fact that the Iterators can not be reset ? What is irregular in that ?). Regardless of what editors think about Java as a language, this section can only confuse readers. At least, what I suggest is : strip the article to the bone, just making a list of important issues (real or perceived), like speed, memory consumption, L&F, and link to another created article, with all the Criticisms. Hervegirod 23:12, 9 June 2006 (UTC)
the infobox lists java having influenced javascript. The text itself admits java and javascript are only distantly related. Shouldn't javascript be removed from the infobox? Ideogram 22:43, 29 May 2006 (UTC)
The names suggest they are related but that is just misleading marketing rubbish, is is enlightening to clarify the difference. Gene Thomas 14:39, 4 June 2006 (UTC)
in Javascript the definitive guide (published by Oreilly) 4th edition in the first chapter it says that javascript and java are not related whatsoever. javascript was going to be named LiveScript but they changed the name at the last moment. this might want to be added, but probably not in the exact words as the book because i'm quite sure that if you did that you would get in a lot of copyright trouble. Javawizard 22:20, 19 October 2006 (MDT)
I have put up Forth as a featured article candidate. Please participate in discussing how it can be improved to match this article in quality. Ideogram 07:21, 4 June 2006 (UTC)
3.1.1 Stand-alone application: has what appears to be rendering errors in the text, It shows
[http://java.sun.com/j2se/1.5.0/docs/api/java/lang/System.html#out out]
.
in the output, the source wiki is
'''{{Javadoc:SE|name=out|java/lang|System|out}}'''
but is being rendered wrong, I didn't know Wikipedia(media) knew about Javadoc, is the engine broken or are the tranformations configured somehere. Either way it is broken. Gene Thomas 14:43, 4 June 2006 (UTC)
I have removed the entire section because it is already verbatim in the Java criticisms article, which is linked in this article. The length of the criticism section was surely confusing for newcomers, especially this particular section. Plus this section seems original research Hervegirod 19:47, 12 June 2006 (UTC)
Hi all -- You might want to be aware of a situation with an anonymous user who is inserting external links to his site at vias.org into various articles. He seems to take online, copylefted books, and mirror them on his own site, with ads. There's nothing illegal about what he's doing, provided he complies with the terms of the license, but I think it's more appropriate to link to the version of the book on the author's own site. This happened in this article with Downey's book, and I've changed the link so it points to the copy maintained by Downey himself.-- Fashionslide 21:17, 15 June 2006 (UTC)
I have renamed external links section "Alternatives" to "Java Implementations". The section was giving an impression that the ones mentioned are "second class" to some "One true Java". However it is not the case. There are a number of Java implementations, some are proprietary and some are free/open source. I have classified them as such. Mritunjai 06:10, 19 June 2006 (UTC)
I reverted the change to the 'Major Implementation' part of the info box at the top, but forgot to leave a comment saying why - my feeling is that netbeans and jbuilder are just development environments, not implementations of Java. As I understand it, if this field is to filled out, it should include the Sun implementation, the IBM one, probably Kaffe and some of the other free versions, and maybe Classpath and the gcc/java toolchain. Batneil 11:41, 18 July 2006 (UTC)
Shouldn't this edit have taken care of itself: [1] :-) kenj0418 18:50, 27 July 2006 (UTC)
Folks, it is really simple: get rid of the lists. Turn them into prose or axe them. If you want this article to get back to FA, think "Tiger Book". The O'Rielly introductory book on Java does have some lists, but the content is not 50% lists. Think prose. List-oriented Java programmers should not contribute if they are tempted to create another list in the prose. See Johnny Cash lists for one way to get the lists out of the main FA-track article. -- 75.26.4.200 23:24, 1 August 2006 (UTC)
I think that the claim that primitive types are not objects does not belong in this section (I'm not saying that the lack of tuples, operator overloading, multiple inheritance, and class properties can not be criticized) Hervegirod 11:01, 7 August 2006 (UTC)
Hi all,
I am not promoting this article for a few reasons. The History section could use improvement (e.g. more details/references), especially the claim that Java is "fairly secure" (what is meant by this, who said it). I've heard of the five goals before but where did they come from, this needs a citation or source. Beyond these two issues I see no other major problems with article, so feel free to renominate the article when these issues are addressed.
Cedars 14:23, 8 August 2006 (UTC)
I object to the following inaccurate statement (second paragraph of the page):
"The language itself borrows much syntax from C and C++ but has a simpler object model and fewer low-level facilities."
Wikipedia's article on Java (Sun) directly contradicts that statement in its History section.
http://en.wikipedia.org/wiki/Java_%28Sun%29#History
which says:
"Back in 1990, Engineer Patrick Naughton had become increasingly frustrated with the state of Sun's C++ and C APIs (application programming interfaces) and tools. While considering moving to NeXT, Naughton was offered a chance to work on new technology and thus the Stealth Project was started."
Java largely grew out of a rejection of C++ and its syntax. Naughton and Gosling largely patterned the language after Objective-C (not C++), SmallTalk and Simula68.
As further evidence of this, check Patrick Naughton's own words, here:
http://www.cs.umd.edu/~seanl/stuff/java-objc.html
Jwisa 03:55, 23 August 2006 (UTC)Jerry W. Walker
I was reviewing the links in the article and noticed that a few of the portals have Google-ads; I know that Google ads don't automatically disqualify a site from inclusion, but I'm wondering if we really any of them. (A Google search will turn up scores of Java and programming portals). Below is a case-by-case review of the current links. Comments are appreciated. OhNoitsJamie Talk 20:04, 1 September 2006 (UTC)
Java programming language → Java (programming language) – Conformance with WP naming conventions
The result of the debate was move as outlined. -- tariqabjotu 02:43, 7 September 2006 (UTC)
Note: This poll has been transcluded onto the talk pages of a number of individual programming languages, but is in fact a subpage of Wikipedia talk:WikiProject Programming languages. When you comment, please note that this survey is for multiple programming languages, not just the one you saw it on.
Some editors have proposed a general rename of articles named with the pattern "FOO programming language" to the pattern "FOO (programming language)". Please note that this poll only is applicable to those programming languages whose names alone would introduce ambiguity. For example, programming languages such as Java and C , whose names alone are ambiguous, would be at Java (programming language) and C (programming language), respectively. Unique names such as Fortran and COBOL, should remain at their respective simple names.
For instructions on how to add a poll participation request to additional applicable article talk pages, please see: Wikipedia talk:WikiProject Programming languages#Poll procedure
Please add "* Support" or "* Oppose" followed by an optional brief explanation, then sign your opinion with ~~~~
In order to reduce clutter in the voting section, i've deicded to respond to DNewhall's vote here. If you're afraid of the amount of work it would take to move the articles, I can move most of them and i'm sure there are other editors willing to take up the task. Also, most books about programming languages simply have the title or common name of the programming language as the title of the book -- the Wrox series uses "Professional PHP" or "professional Java", not "professional PHP programming language" or "professional Java programming langauge". Many of the books I have also have the sorting information as "Computers -- Programming languages -- X," where X is the programming language. atanamir 23:36, 1 September 2006 (UTC)
Imagine if you have a set of objects which all fall under the same category -- let's say they're all different types of Widgets. The types are Alboo, Kabloo, Hello, Wawoob, Baboon, Choogoo, Chimpanzee, etc. Because some will cause ambiguity -- Hello, Baboon, and Chimpanzee -- they need to be disambiguated. However, since the common name (in this case, the real name) is "Hello," "Baboon," and "Chimpanzee," wikipedia has an established precedent of using parentheses. Thus, the unique widgets, Alboo, Kabloo, Wawoob, Coogoo, can have articles simply at the name itself; but the ambiguous names should have articles at Hello (widget), Baboon (widget), and Chimpanzee (widget). Thus, the article titles will be uniform in that they are all "at" the name itself, but with a disambiguator on several of them. This is easier than making all of the articles at Alboo widget, Kabloo widget, Hello widget, etc. Also, it allows for the pipe trick, so links can easily be made with [[Hello (widget)|]] --> Hello. atanamir 23:54, 1 September 2006 (UTC)
Even if we add the parentheses, the guideline at Wikipedia:Disambiguation#Specific topic makes sense to me:
If there is a choice between disambiguating with a generic class or with a context, choose whichever is simpler. Use the same disambiguating phrase for other topics within the same context.
- For example, "(mythology)" rather than "(mythological figure)".
In this case, we could have the simpler and more widely applicable "(computing)" instead of the long "(programming language)". -- TuukkaH 10:04, 2 September 2006 (UTC)
To meet the new standard, the pages should be moved to something like Criticism of C (programming language), right? examples are Georgia (U.S. State) and Politics of Georgia (U.S. state). atanamir 02:42, 5 September 2006 (UTC)
Question 1: What is "runtime?" This term is mentioned at the beginning of the article, but it is not explained. There definitely needs to be an article about it.
Question 2: What is "compilation overhead?" This term is mentioned in the "Platform Independence" section, but it is not explained. Perhaps there should be an article about it.
Question 3: What is a "widget" in this context? This term is mentioned in the "Look and feel" section, but it is not explained. Perhaps there should be an article about it. —Preceding unsigned comment added by Oatmealcookiemon ( talk • contribs)
I deleted the part about tuples, operator overloading, etc... and put it in the specific article, in the Java criticisms#Language choices section. I did this because I think that the main criticims about Java is about the fact that there are primitive types, not all is Object. I really think we ought to delete this part from the main article, because is obscures what is important for the reader (plus it is easily accessible in another article linked to this part). Explaining why it is important / not important to have tuples, operator overloading, multiple inheritance would not be possible in the limited space of this section. People still argue about whether it is important or not to have multiple inheritance, for example... Hervegirod 19:37, 17 September 2006 (UTC)
sir i want to know wheteher the java is opensource and/ or freeware any body know this plz clear this
The performance criticisms refer to Java as an interpreted language. This is not correct. Java is a compiled language that is compiled (in the typical case) to Java byte code. The byte code is executed by a virtual machine, that can be implemented in a number of ways, interpreted execution being only one of those. So it seems to me that this criticism should be in article on the Java virtual machine and not here. Criticisms here should focus on the language itself, and not on the execution environment—if the execution environment is going to be discussed, it needs a more comprehensive treatment than some criticisms of some implementations. If I don't hear any objections in the next couple days I'm going to refactor the performance criticisms to remove discussion of Java as an interpreted language. — Doug Bell talk• contrib 16:28, 30 October 2006 (UTC)
Whether Java is interpetive or compiled, there remains a serious performance issue that needs to be addressed and resolved in an objective fashion. I believe that it is generally quite evident that typical Java applications require an inordinate amount of processor time and produce noticable interactive latency, especially when compared to similar C language programs. This is even true with many commercial programs.
I suggest three reasons for this is 1) Java's portable nature prevents it from being tailored to a specific platform 2) Its object-oriented nature prevents low-level optimization and 3) Its automatic garbage collection causes a major performance hit because of inefficient use of memory.
It would be a great service and benefit to the user community if someone more knowledgable than myself could investigate this performance issue and report on it. I fear that too many programers are misguided and consequently make the wrong decision in choosing a language for a new application. Roesser 22:26, 6 July 2007 (UTC)
I suggest to keep the code examples in the article conforming to the standard convention on coding style as defined by Sun. In particular, the curly braces should not be on their own line. -- int19h 09:37, 1 November 2006 (UTC)
OOP is under Object-oriented programming. The section discussing OOP does not pertain directly to Java, but is simply a summary of the concept. I linked it to the main page, but I would suggest removing it completely Jabberrock 10:01, 4 November 2006 (UTC)
Extensions and related architectures, Java Specification Requests, the list of IDEs, and many of the other external links need to be cut down. However, would it be a better idea to instead place them into their own articles (ie: List of Java Integrated Development Environments)? Gimmekat 15:45, 9 November 2006 (UTC)
I believe that Java was originally created for small devices like PDAs. Gosling et al wanted to create a language to address what looked like a plethora of possible operating systems with the "write once run anywhere" solution. At some point they realized that the idea provided a larger solution than just PDAs and phones.
Below is a quote from a Sun article verifying this. You can find the article here [ [4]]:
"Java technology was created as a programming tool in a small, closed-door project initiated by Patrick Naughton, Mike Sheridan, and James Gosling of Sun in 1991. But creating a new language wasn't even the point of "the Green Project."
To demonstrate what they saw as a possible future in digital devices, the Green Team locked themselves away in an anonymous office on Sand Hill Road in Menlo Park, cut all regular communications with Sun, and worked around the clock for 18 months. In the summer of 1992, they emerged with a working demo, an interactive, handheld home-entertainment device controller with an animated touchscreen user interface.
In the demo, the now familiar Java technology mascot, Duke, was shown waving and doing cartwheels on the screen. The device was called *7 ("StarSeven"), named after an "answer your phone from any extension" feature of the phone system in the Green Team office. Duke was actually a representation of the *7's "agent", a software entity that did tasks on behalf of the user. "
Regards, H. Hall
Are the java class libraries GPL and/or publicaly available? mrholybrain 's talk 02:33, 20 November 2006 (UTC)
i just noticed that the explanation of what happens in the swing sample isn't exactly accurate with what is in the sample itself. someone might want to update the description of the code sample. —Preceding unsigned comment added by 67.182.233.113 ( talk • contribs)
import javax.swing.*;
public class SwingHelloWorld extends JFrame
{
public SwingHelloWorld()
{
super("Swing - Hello World");
setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
JLabel label = new JLabel("Hello World");
add(label);
pack();
setVisible(true);
}
public static void main(String[] args)
{
javax.swing.SwingUtilities.invokeLater(new Runnable() {
public void run() {
new SwingHelloWorld();
}
});
}
}
javax.swing.SwingUtilities.invokeLater
should also be in any swing application as it appears in all Swing Tutorials samples from Sun.Java is also used as BD-J in Blu-ray, maybe someone can add this to the java article (I'm not that good with writing :). —The preceding unsigned comment was added by 87.213.0.34 ( talk) 12:50, 12 January 2007 (UTC).
Note that, although there's an explicit compiling stage, at some point, the Java bytecode is interpreted or converted to native machine instructions by the JIT compiler.
There is a third option - the bytecode can be compiled to machine code prior to execution, resulting in a stand-alone native application.
Also, this section might mention that the bytecode is as specified in the "Java Virtual Machine Specification".
![]() | This is an archive of past discussions. 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. |
Archive 1 | ← | Archive 3 | Archive 4 | Archive 5 | Archive 6 | Archive 7 |
The License section of the Criticisms section refers solely to Sun's implementation of Java stating that "Java [...] cannot be included in projects [...] such as Debian". This is not true, Debian does include a Java compiler, albeit an incomplete one, in the form of GCJ.
I'm not suggesting that the problems of Sun's Java implementation and its decendands which is the predomenant one should be downplayed, merely that the distinction between the two needs to be made clear to the reader, and the article does a very poor job of informing the reader about which it is referring to at any time, using the blanket term "Java" for everything, which is ambiguous. -- Ævar Arnfjörð Bjarmason 18:59, 29 May 2006 (UTC)
This Criticisms section really has gone too far. This section needs to be stripped of what does not belong in it (roughtly, almost all the text), and present a real SYNTHESIS of common critics about Java. I don't think the "language irregularities" is in the right place too (for example, why putting in irregularities the fact that the Iterators can not be reset ? What is irregular in that ?). Regardless of what editors think about Java as a language, this section can only confuse readers. At least, what I suggest is : strip the article to the bone, just making a list of important issues (real or perceived), like speed, memory consumption, L&F, and link to another created article, with all the Criticisms. Hervegirod 23:12, 9 June 2006 (UTC)
the infobox lists java having influenced javascript. The text itself admits java and javascript are only distantly related. Shouldn't javascript be removed from the infobox? Ideogram 22:43, 29 May 2006 (UTC)
The names suggest they are related but that is just misleading marketing rubbish, is is enlightening to clarify the difference. Gene Thomas 14:39, 4 June 2006 (UTC)
in Javascript the definitive guide (published by Oreilly) 4th edition in the first chapter it says that javascript and java are not related whatsoever. javascript was going to be named LiveScript but they changed the name at the last moment. this might want to be added, but probably not in the exact words as the book because i'm quite sure that if you did that you would get in a lot of copyright trouble. Javawizard 22:20, 19 October 2006 (MDT)
I have put up Forth as a featured article candidate. Please participate in discussing how it can be improved to match this article in quality. Ideogram 07:21, 4 June 2006 (UTC)
3.1.1 Stand-alone application: has what appears to be rendering errors in the text, It shows
[http://java.sun.com/j2se/1.5.0/docs/api/java/lang/System.html#out out]
.
in the output, the source wiki is
'''{{Javadoc:SE|name=out|java/lang|System|out}}'''
but is being rendered wrong, I didn't know Wikipedia(media) knew about Javadoc, is the engine broken or are the tranformations configured somehere. Either way it is broken. Gene Thomas 14:43, 4 June 2006 (UTC)
I have removed the entire section because it is already verbatim in the Java criticisms article, which is linked in this article. The length of the criticism section was surely confusing for newcomers, especially this particular section. Plus this section seems original research Hervegirod 19:47, 12 June 2006 (UTC)
Hi all -- You might want to be aware of a situation with an anonymous user who is inserting external links to his site at vias.org into various articles. He seems to take online, copylefted books, and mirror them on his own site, with ads. There's nothing illegal about what he's doing, provided he complies with the terms of the license, but I think it's more appropriate to link to the version of the book on the author's own site. This happened in this article with Downey's book, and I've changed the link so it points to the copy maintained by Downey himself.-- Fashionslide 21:17, 15 June 2006 (UTC)
I have renamed external links section "Alternatives" to "Java Implementations". The section was giving an impression that the ones mentioned are "second class" to some "One true Java". However it is not the case. There are a number of Java implementations, some are proprietary and some are free/open source. I have classified them as such. Mritunjai 06:10, 19 June 2006 (UTC)
I reverted the change to the 'Major Implementation' part of the info box at the top, but forgot to leave a comment saying why - my feeling is that netbeans and jbuilder are just development environments, not implementations of Java. As I understand it, if this field is to filled out, it should include the Sun implementation, the IBM one, probably Kaffe and some of the other free versions, and maybe Classpath and the gcc/java toolchain. Batneil 11:41, 18 July 2006 (UTC)
Shouldn't this edit have taken care of itself: [1] :-) kenj0418 18:50, 27 July 2006 (UTC)
Folks, it is really simple: get rid of the lists. Turn them into prose or axe them. If you want this article to get back to FA, think "Tiger Book". The O'Rielly introductory book on Java does have some lists, but the content is not 50% lists. Think prose. List-oriented Java programmers should not contribute if they are tempted to create another list in the prose. See Johnny Cash lists for one way to get the lists out of the main FA-track article. -- 75.26.4.200 23:24, 1 August 2006 (UTC)
I think that the claim that primitive types are not objects does not belong in this section (I'm not saying that the lack of tuples, operator overloading, multiple inheritance, and class properties can not be criticized) Hervegirod 11:01, 7 August 2006 (UTC)
Hi all,
I am not promoting this article for a few reasons. The History section could use improvement (e.g. more details/references), especially the claim that Java is "fairly secure" (what is meant by this, who said it). I've heard of the five goals before but where did they come from, this needs a citation or source. Beyond these two issues I see no other major problems with article, so feel free to renominate the article when these issues are addressed.
Cedars 14:23, 8 August 2006 (UTC)
I object to the following inaccurate statement (second paragraph of the page):
"The language itself borrows much syntax from C and C++ but has a simpler object model and fewer low-level facilities."
Wikipedia's article on Java (Sun) directly contradicts that statement in its History section.
http://en.wikipedia.org/wiki/Java_%28Sun%29#History
which says:
"Back in 1990, Engineer Patrick Naughton had become increasingly frustrated with the state of Sun's C++ and C APIs (application programming interfaces) and tools. While considering moving to NeXT, Naughton was offered a chance to work on new technology and thus the Stealth Project was started."
Java largely grew out of a rejection of C++ and its syntax. Naughton and Gosling largely patterned the language after Objective-C (not C++), SmallTalk and Simula68.
As further evidence of this, check Patrick Naughton's own words, here:
http://www.cs.umd.edu/~seanl/stuff/java-objc.html
Jwisa 03:55, 23 August 2006 (UTC)Jerry W. Walker
I was reviewing the links in the article and noticed that a few of the portals have Google-ads; I know that Google ads don't automatically disqualify a site from inclusion, but I'm wondering if we really any of them. (A Google search will turn up scores of Java and programming portals). Below is a case-by-case review of the current links. Comments are appreciated. OhNoitsJamie Talk 20:04, 1 September 2006 (UTC)
Java programming language → Java (programming language) – Conformance with WP naming conventions
The result of the debate was move as outlined. -- tariqabjotu 02:43, 7 September 2006 (UTC)
Note: This poll has been transcluded onto the talk pages of a number of individual programming languages, but is in fact a subpage of Wikipedia talk:WikiProject Programming languages. When you comment, please note that this survey is for multiple programming languages, not just the one you saw it on.
Some editors have proposed a general rename of articles named with the pattern "FOO programming language" to the pattern "FOO (programming language)". Please note that this poll only is applicable to those programming languages whose names alone would introduce ambiguity. For example, programming languages such as Java and C , whose names alone are ambiguous, would be at Java (programming language) and C (programming language), respectively. Unique names such as Fortran and COBOL, should remain at their respective simple names.
For instructions on how to add a poll participation request to additional applicable article talk pages, please see: Wikipedia talk:WikiProject Programming languages#Poll procedure
Please add "* Support" or "* Oppose" followed by an optional brief explanation, then sign your opinion with ~~~~
In order to reduce clutter in the voting section, i've deicded to respond to DNewhall's vote here. If you're afraid of the amount of work it would take to move the articles, I can move most of them and i'm sure there are other editors willing to take up the task. Also, most books about programming languages simply have the title or common name of the programming language as the title of the book -- the Wrox series uses "Professional PHP" or "professional Java", not "professional PHP programming language" or "professional Java programming langauge". Many of the books I have also have the sorting information as "Computers -- Programming languages -- X," where X is the programming language. atanamir 23:36, 1 September 2006 (UTC)
Imagine if you have a set of objects which all fall under the same category -- let's say they're all different types of Widgets. The types are Alboo, Kabloo, Hello, Wawoob, Baboon, Choogoo, Chimpanzee, etc. Because some will cause ambiguity -- Hello, Baboon, and Chimpanzee -- they need to be disambiguated. However, since the common name (in this case, the real name) is "Hello," "Baboon," and "Chimpanzee," wikipedia has an established precedent of using parentheses. Thus, the unique widgets, Alboo, Kabloo, Wawoob, Coogoo, can have articles simply at the name itself; but the ambiguous names should have articles at Hello (widget), Baboon (widget), and Chimpanzee (widget). Thus, the article titles will be uniform in that they are all "at" the name itself, but with a disambiguator on several of them. This is easier than making all of the articles at Alboo widget, Kabloo widget, Hello widget, etc. Also, it allows for the pipe trick, so links can easily be made with [[Hello (widget)|]] --> Hello. atanamir 23:54, 1 September 2006 (UTC)
Even if we add the parentheses, the guideline at Wikipedia:Disambiguation#Specific topic makes sense to me:
If there is a choice between disambiguating with a generic class or with a context, choose whichever is simpler. Use the same disambiguating phrase for other topics within the same context.
- For example, "(mythology)" rather than "(mythological figure)".
In this case, we could have the simpler and more widely applicable "(computing)" instead of the long "(programming language)". -- TuukkaH 10:04, 2 September 2006 (UTC)
To meet the new standard, the pages should be moved to something like Criticism of C (programming language), right? examples are Georgia (U.S. State) and Politics of Georgia (U.S. state). atanamir 02:42, 5 September 2006 (UTC)
Question 1: What is "runtime?" This term is mentioned at the beginning of the article, but it is not explained. There definitely needs to be an article about it.
Question 2: What is "compilation overhead?" This term is mentioned in the "Platform Independence" section, but it is not explained. Perhaps there should be an article about it.
Question 3: What is a "widget" in this context? This term is mentioned in the "Look and feel" section, but it is not explained. Perhaps there should be an article about it. —Preceding unsigned comment added by Oatmealcookiemon ( talk • contribs)
I deleted the part about tuples, operator overloading, etc... and put it in the specific article, in the Java criticisms#Language choices section. I did this because I think that the main criticims about Java is about the fact that there are primitive types, not all is Object. I really think we ought to delete this part from the main article, because is obscures what is important for the reader (plus it is easily accessible in another article linked to this part). Explaining why it is important / not important to have tuples, operator overloading, multiple inheritance would not be possible in the limited space of this section. People still argue about whether it is important or not to have multiple inheritance, for example... Hervegirod 19:37, 17 September 2006 (UTC)
sir i want to know wheteher the java is opensource and/ or freeware any body know this plz clear this
The performance criticisms refer to Java as an interpreted language. This is not correct. Java is a compiled language that is compiled (in the typical case) to Java byte code. The byte code is executed by a virtual machine, that can be implemented in a number of ways, interpreted execution being only one of those. So it seems to me that this criticism should be in article on the Java virtual machine and not here. Criticisms here should focus on the language itself, and not on the execution environment—if the execution environment is going to be discussed, it needs a more comprehensive treatment than some criticisms of some implementations. If I don't hear any objections in the next couple days I'm going to refactor the performance criticisms to remove discussion of Java as an interpreted language. — Doug Bell talk• contrib 16:28, 30 October 2006 (UTC)
Whether Java is interpetive or compiled, there remains a serious performance issue that needs to be addressed and resolved in an objective fashion. I believe that it is generally quite evident that typical Java applications require an inordinate amount of processor time and produce noticable interactive latency, especially when compared to similar C language programs. This is even true with many commercial programs.
I suggest three reasons for this is 1) Java's portable nature prevents it from being tailored to a specific platform 2) Its object-oriented nature prevents low-level optimization and 3) Its automatic garbage collection causes a major performance hit because of inefficient use of memory.
It would be a great service and benefit to the user community if someone more knowledgable than myself could investigate this performance issue and report on it. I fear that too many programers are misguided and consequently make the wrong decision in choosing a language for a new application. Roesser 22:26, 6 July 2007 (UTC)
I suggest to keep the code examples in the article conforming to the standard convention on coding style as defined by Sun. In particular, the curly braces should not be on their own line. -- int19h 09:37, 1 November 2006 (UTC)
OOP is under Object-oriented programming. The section discussing OOP does not pertain directly to Java, but is simply a summary of the concept. I linked it to the main page, but I would suggest removing it completely Jabberrock 10:01, 4 November 2006 (UTC)
Extensions and related architectures, Java Specification Requests, the list of IDEs, and many of the other external links need to be cut down. However, would it be a better idea to instead place them into their own articles (ie: List of Java Integrated Development Environments)? Gimmekat 15:45, 9 November 2006 (UTC)
I believe that Java was originally created for small devices like PDAs. Gosling et al wanted to create a language to address what looked like a plethora of possible operating systems with the "write once run anywhere" solution. At some point they realized that the idea provided a larger solution than just PDAs and phones.
Below is a quote from a Sun article verifying this. You can find the article here [ [4]]:
"Java technology was created as a programming tool in a small, closed-door project initiated by Patrick Naughton, Mike Sheridan, and James Gosling of Sun in 1991. But creating a new language wasn't even the point of "the Green Project."
To demonstrate what they saw as a possible future in digital devices, the Green Team locked themselves away in an anonymous office on Sand Hill Road in Menlo Park, cut all regular communications with Sun, and worked around the clock for 18 months. In the summer of 1992, they emerged with a working demo, an interactive, handheld home-entertainment device controller with an animated touchscreen user interface.
In the demo, the now familiar Java technology mascot, Duke, was shown waving and doing cartwheels on the screen. The device was called *7 ("StarSeven"), named after an "answer your phone from any extension" feature of the phone system in the Green Team office. Duke was actually a representation of the *7's "agent", a software entity that did tasks on behalf of the user. "
Regards, H. Hall
Are the java class libraries GPL and/or publicaly available? mrholybrain 's talk 02:33, 20 November 2006 (UTC)
i just noticed that the explanation of what happens in the swing sample isn't exactly accurate with what is in the sample itself. someone might want to update the description of the code sample. —Preceding unsigned comment added by 67.182.233.113 ( talk • contribs)
import javax.swing.*;
public class SwingHelloWorld extends JFrame
{
public SwingHelloWorld()
{
super("Swing - Hello World");
setDefaultCloseOperation(JFrame.EXIT_ON_CLOSE);
JLabel label = new JLabel("Hello World");
add(label);
pack();
setVisible(true);
}
public static void main(String[] args)
{
javax.swing.SwingUtilities.invokeLater(new Runnable() {
public void run() {
new SwingHelloWorld();
}
});
}
}
javax.swing.SwingUtilities.invokeLater
should also be in any swing application as it appears in all Swing Tutorials samples from Sun.Java is also used as BD-J in Blu-ray, maybe someone can add this to the java article (I'm not that good with writing :). —The preceding unsigned comment was added by 87.213.0.34 ( talk) 12:50, 12 January 2007 (UTC).
Note that, although there's an explicit compiling stage, at some point, the Java bytecode is interpreted or converted to native machine instructions by the JIT compiler.
There is a third option - the bytecode can be compiled to machine code prior to execution, resulting in a stand-alone native application.
Also, this section might mention that the bytecode is as specified in the "Java Virtual Machine Specification".