Fun with Java
-
For the past 4 months or so, I have tried to keep my brain from atrofying by working on complex issues. I am approaching 80 and dementia in all forms is one of the few things that really scares me. When my daughter was struggling with a course in elementary Java, I had to quickly learn elementary Java to help her. Well, Java hooked me, and now I am well into Javafx with fxml and far, far beyond her elementary course. I found Java to be quite similar to C#, but at the same time, it had significant differences. One difference that drove me nuts several times, is the simple act to compare strings. In C# I must have have done the comparison like: if (stringA == stringB) { } thousands of times. But try to do that in Java, ooh boy! The compiler will just ignore the statement and skip to the next statement. No exception, no error, no nothing. It just ignores the line. The results can be chaotic with absolutely no indication where the error occurred! The proper syntax in Java is: if ( stringA.equals(stringB)) { } And if any of you readers tell me I deserve to suffer for trying to work in Java: I will scream! :-D One other thing: I started out using the Eclipse IDE for java, but soon found I preferred the IntelliJ IDE. In fact IntelliJ is better than Visual Studio in several respects. But VS admittedly has its moments in the sun.
Get me coffee and no one gets hurt!
-
Cp-Coder wrote:
The proper syntax in Java is: if ( stringA.equals(stringB)) { }
You can do that in c# too.
In .Net stringA==stringB invokes stringA.equals(stringB). In Java stringA==stringB isn't ignored. It compares the object references, which similar to Object.ReferenceEquals(A, B).
-
For the past 4 months or so, I have tried to keep my brain from atrofying by working on complex issues. I am approaching 80 and dementia in all forms is one of the few things that really scares me. When my daughter was struggling with a course in elementary Java, I had to quickly learn elementary Java to help her. Well, Java hooked me, and now I am well into Javafx with fxml and far, far beyond her elementary course. I found Java to be quite similar to C#, but at the same time, it had significant differences. One difference that drove me nuts several times, is the simple act to compare strings. In C# I must have have done the comparison like: if (stringA == stringB) { } thousands of times. But try to do that in Java, ooh boy! The compiler will just ignore the statement and skip to the next statement. No exception, no error, no nothing. It just ignores the line. The results can be chaotic with absolutely no indication where the error occurred! The proper syntax in Java is: if ( stringA.equals(stringB)) { } And if any of you readers tell me I deserve to suffer for trying to work in Java: I will scream! :-D One other thing: I started out using the Eclipse IDE for java, but soon found I preferred the IntelliJ IDE. In fact IntelliJ is better than Visual Studio in several respects. But VS admittedly has its moments in the sun.
Get me coffee and no one gets hurt!
Only approaching 70 here. Since I retired 4 years ago I keep dementia at bay by: a) Writing and publishing Android apps in Java using Android Studio which is based on IntelliJ. b) Learning French. I am now up to reading one French novel every week for the last year. Everything you need for both these activities is available free or quite cheaply online. One of my apps: https://play.google.com/store/apps/details?id=net.globalrecordings.fivefish&hl=en_AU&gl=US[^]
-
For the past 4 months or so, I have tried to keep my brain from atrofying by working on complex issues. I am approaching 80 and dementia in all forms is one of the few things that really scares me. When my daughter was struggling with a course in elementary Java, I had to quickly learn elementary Java to help her. Well, Java hooked me, and now I am well into Javafx with fxml and far, far beyond her elementary course. I found Java to be quite similar to C#, but at the same time, it had significant differences. One difference that drove me nuts several times, is the simple act to compare strings. In C# I must have have done the comparison like: if (stringA == stringB) { } thousands of times. But try to do that in Java, ooh boy! The compiler will just ignore the statement and skip to the next statement. No exception, no error, no nothing. It just ignores the line. The results can be chaotic with absolutely no indication where the error occurred! The proper syntax in Java is: if ( stringA.equals(stringB)) { } And if any of you readers tell me I deserve to suffer for trying to work in Java: I will scream! :-D One other thing: I started out using the Eclipse IDE for java, but soon found I preferred the IntelliJ IDE. In fact IntelliJ is better than Visual Studio in several respects. But VS admittedly has its moments in the sun.
Get me coffee and no one gets hurt!
i'm really glad you have fun. i'm slowly approaching 50 and building up empathy for persons of older age, respect is granted. i must admit, that is the first time i hear 'fun' and 'java' in the same sentence :) maybe java operator == compares strings by their reference? JetBrains, the creators of IntelliJ IDE are known for making superb software. i hope you have lot's of fun
-
For the past 4 months or so, I have tried to keep my brain from atrofying by working on complex issues. I am approaching 80 and dementia in all forms is one of the few things that really scares me. When my daughter was struggling with a course in elementary Java, I had to quickly learn elementary Java to help her. Well, Java hooked me, and now I am well into Javafx with fxml and far, far beyond her elementary course. I found Java to be quite similar to C#, but at the same time, it had significant differences. One difference that drove me nuts several times, is the simple act to compare strings. In C# I must have have done the comparison like: if (stringA == stringB) { } thousands of times. But try to do that in Java, ooh boy! The compiler will just ignore the statement and skip to the next statement. No exception, no error, no nothing. It just ignores the line. The results can be chaotic with absolutely no indication where the error occurred! The proper syntax in Java is: if ( stringA.equals(stringB)) { } And if any of you readers tell me I deserve to suffer for trying to work in Java: I will scream! :-D One other thing: I started out using the Eclipse IDE for java, but soon found I preferred the IntelliJ IDE. In fact IntelliJ is better than Visual Studio in several respects. But VS admittedly has its moments in the sun.
Get me coffee and no one gets hurt!
The word for the day: "to keep my brain from atrofying ..." Correction: "atrofrying" Meaning: being fried and then atrophying :laugh:
-
For the past 4 months or so, I have tried to keep my brain from atrofying by working on complex issues. I am approaching 80 and dementia in all forms is one of the few things that really scares me. When my daughter was struggling with a course in elementary Java, I had to quickly learn elementary Java to help her. Well, Java hooked me, and now I am well into Javafx with fxml and far, far beyond her elementary course. I found Java to be quite similar to C#, but at the same time, it had significant differences. One difference that drove me nuts several times, is the simple act to compare strings. In C# I must have have done the comparison like: if (stringA == stringB) { } thousands of times. But try to do that in Java, ooh boy! The compiler will just ignore the statement and skip to the next statement. No exception, no error, no nothing. It just ignores the line. The results can be chaotic with absolutely no indication where the error occurred! The proper syntax in Java is: if ( stringA.equals(stringB)) { } And if any of you readers tell me I deserve to suffer for trying to work in Java: I will scream! :-D One other thing: I started out using the Eclipse IDE for java, but soon found I preferred the IntelliJ IDE. In fact IntelliJ is better than Visual Studio in several respects. But VS admittedly has its moments in the sun.
Get me coffee and no one gets hurt!
You deserve to suffer for trying to work in Java! Big Grin | :-D
-
For the past 4 months or so, I have tried to keep my brain from atrofying by working on complex issues. I am approaching 80 and dementia in all forms is one of the few things that really scares me. When my daughter was struggling with a course in elementary Java, I had to quickly learn elementary Java to help her. Well, Java hooked me, and now I am well into Javafx with fxml and far, far beyond her elementary course. I found Java to be quite similar to C#, but at the same time, it had significant differences. One difference that drove me nuts several times, is the simple act to compare strings. In C# I must have have done the comparison like: if (stringA == stringB) { } thousands of times. But try to do that in Java, ooh boy! The compiler will just ignore the statement and skip to the next statement. No exception, no error, no nothing. It just ignores the line. The results can be chaotic with absolutely no indication where the error occurred! The proper syntax in Java is: if ( stringA.equals(stringB)) { } And if any of you readers tell me I deserve to suffer for trying to work in Java: I will scream! :-D One other thing: I started out using the Eclipse IDE for java, but soon found I preferred the IntelliJ IDE. In fact IntelliJ is better than Visual Studio in several respects. But VS admittedly has its moments in the sun.
Get me coffee and no one gets hurt!
-
For the past 4 months or so, I have tried to keep my brain from atrofying by working on complex issues. I am approaching 80 and dementia in all forms is one of the few things that really scares me. When my daughter was struggling with a course in elementary Java, I had to quickly learn elementary Java to help her. Well, Java hooked me, and now I am well into Javafx with fxml and far, far beyond her elementary course. I found Java to be quite similar to C#, but at the same time, it had significant differences. One difference that drove me nuts several times, is the simple act to compare strings. In C# I must have have done the comparison like: if (stringA == stringB) { } thousands of times. But try to do that in Java, ooh boy! The compiler will just ignore the statement and skip to the next statement. No exception, no error, no nothing. It just ignores the line. The results can be chaotic with absolutely no indication where the error occurred! The proper syntax in Java is: if ( stringA.equals(stringB)) { } And if any of you readers tell me I deserve to suffer for trying to work in Java: I will scream! :-D One other thing: I started out using the Eclipse IDE for java, but soon found I preferred the IntelliJ IDE. In fact IntelliJ is better than Visual Studio in several respects. But VS admittedly has its moments in the sun.
Get me coffee and no one gets hurt!
Being 71 myself, I can relate. Just learning C#, is more than enough for me. I always worked in VB, still do until I get my code converted. Yes I am still working for a living. Plan ahead! :sigh: :sigh:
Wear a mask! help prevent Covid 19 and its' variants.
-
For the past 4 months or so, I have tried to keep my brain from atrofying by working on complex issues. I am approaching 80 and dementia in all forms is one of the few things that really scares me. When my daughter was struggling with a course in elementary Java, I had to quickly learn elementary Java to help her. Well, Java hooked me, and now I am well into Javafx with fxml and far, far beyond her elementary course. I found Java to be quite similar to C#, but at the same time, it had significant differences. One difference that drove me nuts several times, is the simple act to compare strings. In C# I must have have done the comparison like: if (stringA == stringB) { } thousands of times. But try to do that in Java, ooh boy! The compiler will just ignore the statement and skip to the next statement. No exception, no error, no nothing. It just ignores the line. The results can be chaotic with absolutely no indication where the error occurred! The proper syntax in Java is: if ( stringA.equals(stringB)) { } And if any of you readers tell me I deserve to suffer for trying to work in Java: I will scream! :-D One other thing: I started out using the Eclipse IDE for java, but soon found I preferred the IntelliJ IDE. In fact IntelliJ is better than Visual Studio in several respects. But VS admittedly has its moments in the sun.
Get me coffee and no one gets hurt!
Awesome. 🤩 This grows my expectations to finally 🙏learn Java when get in these times.🤣 After all, enjoy programming is what it matters😃
-
Awesome. 🤩 This grows my expectations to finally 🙏learn Java when get in these times.🤣 After all, enjoy programming is what it matters😃
Good! If you are serious about Java, I recommend you focus on JavaFX with fxml and using the IntelliJ IDE. :) To get started quickly with JavaFX and IntelliJ, I recommend the book "The Definitive Guide to Modern Java with JavaFX" by Chin et al. It's available as a Kindle from Amazon. It will teach you to configure a new project for IntelliJ, which can be a little tricky. Check the section "Setting Up Your Environment". Also the section: "Your First Modern Java Client" Good luck, and let us know how you progress! I am here to assist where I can. Always keep in mind: Java is not for sissies! :laugh:
Get me coffee and no one gets hurt!
-
Being 71 myself, I can relate. Just learning C#, is more than enough for me. I always worked in VB, still do until I get my code converted. Yes I am still working for a living. Plan ahead! :sigh: :sigh:
Wear a mask! help prevent Covid 19 and its' variants.
-
You deserve to suffer for trying to work in Java! Big Grin | :-D
-
Awesome. 🤩 This grows my expectations to finally 🙏learn Java when get in these times.🤣 After all, enjoy programming is what it matters😃
If you are seriously interested in Java, I recommend the book "The Definitive Guide to Modern Java Clients with JavaFX" by Chin et al. It is available from Amazon as a Kindle download. It helped me getting IntelliJ set up and configuring my first app, which is a little tricky. Read the sections: "Setting Up Your Environment" and "Your First Modern Java Client". Good luck! :)
Get me coffee and no one gets hurt!
-
For the past 4 months or so, I have tried to keep my brain from atrofying by working on complex issues. I am approaching 80 and dementia in all forms is one of the few things that really scares me. When my daughter was struggling with a course in elementary Java, I had to quickly learn elementary Java to help her. Well, Java hooked me, and now I am well into Javafx with fxml and far, far beyond her elementary course. I found Java to be quite similar to C#, but at the same time, it had significant differences. One difference that drove me nuts several times, is the simple act to compare strings. In C# I must have have done the comparison like: if (stringA == stringB) { } thousands of times. But try to do that in Java, ooh boy! The compiler will just ignore the statement and skip to the next statement. No exception, no error, no nothing. It just ignores the line. The results can be chaotic with absolutely no indication where the error occurred! The proper syntax in Java is: if ( stringA.equals(stringB)) { } And if any of you readers tell me I deserve to suffer for trying to work in Java: I will scream! :-D One other thing: I started out using the Eclipse IDE for java, but soon found I preferred the IntelliJ IDE. In fact IntelliJ is better than Visual Studio in several respects. But VS admittedly has its moments in the sun.
Get me coffee and no one gets hurt!
Every object in Java inherits the equals method from Object, but the default implementation simply compares the object references (so to be true it must compare the same object instance with itself). It is part of the specs that every class has the equals method implementation replaced to provide the desired functionality.
-
If you are seriously interested in Java, I recommend the book "The Definitive Guide to Modern Java Clients with JavaFX" by Chin et al. It is available from Amazon as a Kindle download. It helped me getting IntelliJ set up and configuring my first app, which is a little tricky. Read the sections: "Setting Up Your Environment" and "Your First Modern Java Client". Good luck! :)
Get me coffee and no one gets hurt!
Sorry for my delay! Thanks for the tip! I definitely will look about it :java: :-D