James Gosling on Apple, Apache, Google, Oracle and the Future of Java
Why Stack Overflow recommends it
Stack Overflow users link it as a primary source for Java design history, especially why goto was removed but kept as a reserved word, and for Gosling's view of JSF's origins.
Recommended by 0 people across 0 different months, 2010 to 2014.
What it is
A Q&A session with Java creator James Gosling, recorded at a Silicon Valley Java User Group event in November 2010. He covers leaving Oracle, Oracle's stewardship of Java, Android's use of Java, Apple deprecating Java, the Apache Software Foundation's worries, and the future of the language.
What people said
Cites Vitalii Fedorenko · 2010-12 · Stack Overflow · on “Is there a goto statement in Java?”
James Gosling created the original JVM with support of goto statements, but then he removed this feature as needless. The main reason goto is unnecessary is that usually it can be replaced with more readable statements (like break/continue ) or by extracting a piece of code into a method. Source: James Gosling, Q&A session [this video]
Cites Daniel Moses · 2013-01 · Stack Overflow · on “What is the equivalent approach of ASP.Net's Page Load method in JSP”
BalusC was right in saying you are comparing apples to oranges. JSF was created in response to asp.net. ( source [this video] @ 47 minutes) It has grown independently and you might do well to look into all the different frameworks and paradigms out there. While JSF will work similar to asp.net there are plenty of alternatives worth exploring. In .NET you might want to look into MVC4. In Java there is Tapestry, Spring MVC, Seams, etc. I would start with wiki comparison and go from there. At your stage in the game I would pick one and try to get familiar with it, than try 2 more to do that same thing. [LINK]
Cites Pragnani Kinnera · 2013-02 · Stack Overflow · on “goto in java supported?”
The Java keyword list specifies the goto keyword, but it is kept reserved. Means it is not used. If you try to use it will show you error This was probably done in case it were to be added to a later version of Java. If goto weren't on the list, and it were added to the language later on, existing code that used the word goto as an identifier (variable name, method name, etcetera) would break. But because goto is a keyword, such code will not even compile in the present, and it remains possible to make it actually do something later on, without breaking existing code. check this video.. James gosling tell about goto [this video] ...he used goto when he designed java compiler
Cites Pragnani Kinnera · 2013-02 · Stack Overflow · on “goto in java supported?”
@user2097804 hi check this video.. James gosling tell about goto...he used goto when he designed java compiler [this video]
Cites rahulserver · 2013-08 · Stack Overflow · on “Is there a way to perform a goto function in Java?”
You can use the continue to move to different labels in code as: public class Label { public static void main(String[] args) { int temp = 0; out: // label for (int i = 0; i < 3; ++i) { System.out.println("I am here"); for (int j = 0; j < 20; ++j) { if(temp==0) { System.out.println("j: " + j); if (j == 1) { temp = j; continue out; // goto label "out" } } } } System.out.println("temp = " + temp); } } The output: I am here j: 0 j: 1 I am here I am here temp = 1 However I won't recommend that you do it. There are tidier ways to do so as James Gosling [LINK] created the original JVM with support of goto statements, but then he removed this feature as needless. The main reason goto is unnecessary
Cites Rahul Tripathi · 2013-10 · Stack Overflow · on “Is Java ByteCode has "indirect jump"?”
EDIT: Completely took the question wrongly. (See below) JVM support goto at bytecode level. You just need libraries like BCEL [LINK] Original answer, on goto in source code: Initially Java [LINK] had goto statements but later versions didnt had it. I think the possible reason could be goto is unnecessary and it can be replaced with more readable statements The goto keyword exists, but it is not implemented. Check this interesting video by James Gosling [this video]
Cites Wim Coenen · 2014-01 · Stack Overflow · on “Why is it allowed to label almost every statement in Java?”
An early unreleased version of java used to have GOTO. In order to jump to any statement with GOTO, you have to be able to label it. Then at some point James Gosling decided that it wasn't a good feature and ripped it out. This involved grepping through all java code that existed at the time and rewriting any GOTO usage; there were 13 uses. (Source: [this video] ) So, like GOTO still being a reserved word, it's a remnant of GOTO support.
Cites corsiKa · 2014-12 · Stack Overflow · on “Java label? Outer, middle, inner”
Early in Java, there was a goto operator. One day, James Gosling decided to remove it [this video] . But, it turned out there was still use in allowing you to use goto inside loops. So how to do this? Well, with named loops (also known as labeled loops) you could have all the good stuff of breaking out of loops without the downsides of goto ridden spaghetti code. So named loops became a thing, and break and continue were allowed to break or continue a loop other than their immediate parent.
Critical anirvan · 2013-04 · Stack Overflow · on “spring mvc form handling without using spring tag”
oh boy, JSF is something i'd stay away from any given day. whatever doubt lingered in my mind about the awfulness of JSF was laid to rest by this fabulous talk by James Gosling — [this video]