You're perfectly welcome to use it of course, as it still works well and does its job. Those are the reasons I'm not a fan of JGrasp.
Other IDE's are already compiling on the fly, so there is less time wasted. A lot of time is wasted compiling, especially when dealing with larger pieces of code. I know I did.ĭespite all of its advances, it still compiles programs slowly. This isn't as big a deal as packages you can just separate your class files into different folders, but this program wont care either way, and I can see many people being lazy and just stuffing all their Java files into the same folder. While it does help ease the learning process for beginners, it introduces a learning curve when those learning are ready to move on to something better.Īs I mentioned before, not organizing classes into projects is poor style and something that should be enforced.
#Jgrasp com code
Actually, I don't think it can even work with classes that belong in a package (you have to delete the code that tells what package the class is from). This helps to organize very large programs. No industry works this way! In the professional world everything will have its own package and classes will be organized in their packages.
This is very beginner-friendly, but there's one problem with this. Any class created is stand-alone and does not belong in any sort of bundle. Other IDE's (Integrated Development Environment) such as Eclipse show you your errors as you make them, saving a lot of time with error-fixing. Errors can be very daunting to fix when the code has gotten very large, and it would take me a long time to fix my mistakes at times. Then when they first go to compile, they are flooded with error messages. Usually they will write write write until they have many lines of code. Many beginners do not think to code slowly and compile often. JGrasp does not show you errors until compile time.
0 kommentar(er)
