Anybody else read the Java thing in the daily news?
-
Java...I have never really seen the point of it, okay it was supposed to run everywhere with Java Virtual Machine (like .NET Framework on some things iPaqs, Pocket PC), not give you direct access to the hardware (like .NET annoying), be royalty free (like .NET Runtime). So all in all it has been replaced has it not (discussion in a Pub with Geeky friends led to "Why the ***** would you use Java, C# pretty much the same plus you can blame Microsharft when it goes wrong!) Plus all the hotshot Java people I know (2) came from C++ to Java back C++ a few years ago... Are there features of Java that aren't anywhere else, whats it unique selling point any one (don't want to start a war just interested.)
Where was dotNet in 1998? Ever hear of MS Java or J-sharp?
Basic history:
MS saw popularity of Java rising.
MS products at the time were VB or else VS C++/MFC
MS tried the embrace, extend, extinguish recipe with Java 1.1,
but Sun sued them over changes and additions MS added to Java
MS stopped their Java implementations at 1.1 as part of a settlement and
agreed to support Sun's applet plugins better in IE.
MS still saw the benefit of the technology, so they switched all of their
Java/VM efforts into dotNET/C# to directly compete with Java.
Look at the original dotNET APIs vs. Java APIs at the time. 1:1 correlation.
Meanwhile, Sun had become too content with the Java 1.2 spec. They thought they
were done!
dotNET caught up to Java and passed it up in terms of functionality.
Sun grudgingly started adding things like generics and enums which they originally
said they would NEVER add.
Thank goodness for the competition or Java 1.2 might have been the last Java version!Reasons for using Java:
It was the best choice in 1998, 1999, etc.
Many Java tools have had hot code replace since 1999. (Huge time savings!)
It is still a good choice today. (Still best for our product)
It is so universal, that there is TONS of free, open Java source out there.
It is multiplatform. (Yes. with no recompilation, it runs on Windows, Mac, Linux)
It was and still is browser deployable.
Silverlight apps are just Java Applets reworked. (Admit it!)
Java Applets will keep working,
but it looks like MS is already trying to kill Silverlight.
Browser deployments of Java can still provide more consistent behavior
cross browser than JavaScript/HTML5.
Java+Eclipse allows for 25,000+ source file recompiles in 10 minutes,
of course, good incremental compiling is
normally subsecond to compile and hot replace
true databases of workspaces/solutions, etc. As far as I can tell,
VS looks like it still scans files for references.
It has been really stable. Code compiled against Java 1.2 12 years ago should still
run fine with 1.7.
If you adopted (and reworked your app) each time MS technology
for database access has changed, how many times would you have done this?NOTE: You should never let any untrusted site run ActiveX, Java, JavaScript, etc. in your browser, EVER! Why did Microsoft have to add the ActiveX kill bits, etc
-
At least .NET doesn't scream at you "I want to update" every hour on the hour. Or at least it seemed to whenever I had the JVM installed. Don't anymore, and avoid anything that wants it.
Ideological Purity is no substitute for being able to stick your thumb down a pipe to stop the water
:thumbsup:
CPallini wrote:
You cannot argue with agile people so just take the extreme approach and shoot him. :Smile:
-
Java...I have never really seen the point of it, okay it was supposed to run everywhere with Java Virtual Machine (like .NET Framework on some things iPaqs, Pocket PC), not give you direct access to the hardware (like .NET annoying), be royalty free (like .NET Runtime). So all in all it has been replaced has it not (discussion in a Pub with Geeky friends led to "Why the ***** would you use Java, C# pretty much the same plus you can blame Microsharft when it goes wrong!) Plus all the hotshot Java people I know (2) came from C++ to Java back C++ a few years ago... Are there features of Java that aren't anywhere else, whats it unique selling point any one (don't want to start a war just interested.)
Actually there are some enterprise frameworks in Java. In general, they are huge structures, used for big projects, with extreme emphasis on modularity and design patterns. So you don't actually "choose" to do Java: it has been already decided for you in the structure maintaining those systems. You can find a lot of that in telecommunications and public institutions. On the other hand, I've seen very few new projects actually being done in Java. Despite the strengths of the community, Java as a language has remained behind the times (the language itself has nothing like dynamic types, LINQ, functions, type inference or async, which make in most cases half of the design patterns obsolete or transparent) and ends up requiring double the code for most tasks. By the time Java 8 will be adopted for real projects (ie all your components will have updated their API etc), it will have become a dinosaur, like COBOL. It's actually in free fall in the Tiobe Index[^].
-
Where was dotNet in 1998? Ever hear of MS Java or J-sharp?
Basic history:
MS saw popularity of Java rising.
MS products at the time were VB or else VS C++/MFC
MS tried the embrace, extend, extinguish recipe with Java 1.1,
but Sun sued them over changes and additions MS added to Java
MS stopped their Java implementations at 1.1 as part of a settlement and
agreed to support Sun's applet plugins better in IE.
MS still saw the benefit of the technology, so they switched all of their
Java/VM efforts into dotNET/C# to directly compete with Java.
Look at the original dotNET APIs vs. Java APIs at the time. 1:1 correlation.
Meanwhile, Sun had become too content with the Java 1.2 spec. They thought they
were done!
dotNET caught up to Java and passed it up in terms of functionality.
Sun grudgingly started adding things like generics and enums which they originally
said they would NEVER add.
Thank goodness for the competition or Java 1.2 might have been the last Java version!Reasons for using Java:
It was the best choice in 1998, 1999, etc.
Many Java tools have had hot code replace since 1999. (Huge time savings!)
It is still a good choice today. (Still best for our product)
It is so universal, that there is TONS of free, open Java source out there.
It is multiplatform. (Yes. with no recompilation, it runs on Windows, Mac, Linux)
It was and still is browser deployable.
Silverlight apps are just Java Applets reworked. (Admit it!)
Java Applets will keep working,
but it looks like MS is already trying to kill Silverlight.
Browser deployments of Java can still provide more consistent behavior
cross browser than JavaScript/HTML5.
Java+Eclipse allows for 25,000+ source file recompiles in 10 minutes,
of course, good incremental compiling is
normally subsecond to compile and hot replace
true databases of workspaces/solutions, etc. As far as I can tell,
VS looks like it still scans files for references.
It has been really stable. Code compiled against Java 1.2 12 years ago should still
run fine with 1.7.
If you adopted (and reworked your app) each time MS technology
for database access has changed, how many times would you have done this?NOTE: You should never let any untrusted site run ActiveX, Java, JavaScript, etc. in your browser, EVER! Why did Microsoft have to add the ActiveX kill bits, etc
"Java Applets will keep working". Actually the amount of people who have Java active on their browser right now is smaller than those who have Silverlight (and this is really bad, when most people move towards HTML5). It's slow, it has been bashed for YEARS for the security failings (while Silverlight had almost none). "Code compiled against Java 1.2 12 years ago should still run fine with 1.7." I cannot count the number of projects I've seen which have been stack in an obscure minor version of java (as in 1.5.21, and not .22 or later) because one of their libraries breaks if you upgrade. I've never seen such a major problem with .NET. But I CAN count the number of projects in Java 1.7 I've seen in production. Zero. " If you adopted (and reworked your app) each time MS technology for database access has changed, how many times would you have done this?" If you adopted (and reworked your app) each time a community project à la mode offered a new way of database access, how many times would you have done this
-
Java...I have never really seen the point of it, okay it was supposed to run everywhere with Java Virtual Machine (like .NET Framework on some things iPaqs, Pocket PC), not give you direct access to the hardware (like .NET annoying), be royalty free (like .NET Runtime). So all in all it has been replaced has it not (discussion in a Pub with Geeky friends led to "Why the ***** would you use Java, C# pretty much the same plus you can blame Microsharft when it goes wrong!) Plus all the hotshot Java people I know (2) came from C++ to Java back C++ a few years ago... Are there features of Java that aren't anywhere else, whats it unique selling point any one (don't want to start a war just interested.)
I've never touched Java, but the thread has aroused my curiosity. And I've got a long weekend. Downloading the NetBeans IDE.
XAlan Burkhart
-
Java...I have never really seen the point of it, okay it was supposed to run everywhere with Java Virtual Machine (like .NET Framework on some things iPaqs, Pocket PC), not give you direct access to the hardware (like .NET annoying), be royalty free (like .NET Runtime). So all in all it has been replaced has it not (discussion in a Pub with Geeky friends led to "Why the ***** would you use Java, C# pretty much the same plus you can blame Microsharft when it goes wrong!) Plus all the hotshot Java people I know (2) came from C++ to Java back C++ a few years ago... Are there features of Java that aren't anywhere else, whats it unique selling point any one (don't want to start a war just interested.)
If you're on android or linux, it gives you a UI what other popular language does that?
-
glennPattonWork wrote:
Are there features of Java that aren't anywhere else, whats it unique selling point any one (don't want to start a war just interested.)
Java was thought at school, even before .NET existed. Before Java, all languages in school were company-agnostic, they'd only use languages that weren't bound to a certain company. It was pushed by the schools, and now it is slowly being replaced by .NET; the platform provides a better integration with the rest of the ecosystem (Office, DB-server), but (logically) it remains popular in the places that have invested much into their Java-systems.
Bastard Programmer from Hell :suss: if you can't read my code, try converting it here[^]
In the begining there was Java and it was good, then came .NET and it was better... :laugh: Seriously, i used to use Java for everything, mostly because that's the language that i was taught at school, right now i only use it if i want cross plataform compatibility in an application (mostly Windows-Linux compatibility) or if a library that does something amazing is only found there, and i believe that its strong point right now, aside from the huge enterprise applications based on Java, is cross plataform compatibility (when you don't like/hate HTML and Javascript).
CEO at: - Rafaga Systems - Para Facturas - Modern Components for the moment...
-
I used to work at a company that sold LARGE printers ($250k+ for a small one) and they used Java for the UI on the printer itself. I asked why they wanted to use Java there and the manager's answer was because if we change the hardware then the Java will still work. The part that the managers did not realize was that the printer was using a version of Solaris that had a custom kernel to talk and control the hardware. Changing the printer to anything else would be massive work, so the entire idea that they could change it to something else and the app would just work was kinda funny. I pointed this out and they didn't have an answer for it.
Steve Maier
You asked, why they used Java for the UI, and your manager was right if they changed the printer the Java part (the UI) will still work, about everything else, i assume, he didn't care. :-D
CEO at: - Rafaga Systems - Para Facturas - Modern Components for the moment...
-
"Java Applets will keep working". Actually the amount of people who have Java active on their browser right now is smaller than those who have Silverlight (and this is really bad, when most people move towards HTML5). It's slow, it has been bashed for YEARS for the security failings (while Silverlight had almost none). "Code compiled against Java 1.2 12 years ago should still run fine with 1.7." I cannot count the number of projects I've seen which have been stack in an obscure minor version of java (as in 1.5.21, and not .22 or later) because one of their libraries breaks if you upgrade. I've never seen such a major problem with .NET. But I CAN count the number of projects in Java 1.7 I've seen in production. Zero. " If you adopted (and reworked your app) each time MS technology for database access has changed, how many times would you have done this?" If you adopted (and reworked your app) each time a community project à la mode offered a new way of database access, how many times would you have done this
tecgoblin wrote:
I cannot count the number of projects I've seen which have been stack in an obscure minor version of java (as in 1.5.21, and not .22 or later) because one of their libraries breaks if you upgrade.
Well, that's what happen when you use undocumented features, and that happens in every language.
tecgoblin wrote:
I've never seen such a major problem with .NET.
That's because your computer have around 4 versions of the .NET Framework installed and Windows manages (juggles) which one you use behind the scenes. But uninstall the .NET Framework 2.0 and try running an app that targets it in the .NET Framework 4.0 and you will see that Java problems seems like a walk in the park.
tecgoblin wrote:
But I CAN count the number of projects in Java 1.7 I've seen in production. Zero.
If you don't see them, doesn't mean they're not there, but anyway Java 1.7 is pretty young (less than a year), and so i can say the same from projects in production in the .NET Framework 4.0 or 4.5.
CEO at: - Rafaga Systems - Para Facturas - Modern Components for the moment...
-
In the begining there was Java and it was good, then came .NET and it was better... :laugh: Seriously, i used to use Java for everything, mostly because that's the language that i was taught at school, right now i only use it if i want cross plataform compatibility in an application (mostly Windows-Linux compatibility) or if a library that does something amazing is only found there, and i believe that its strong point right now, aside from the huge enterprise applications based on Java, is cross plataform compatibility (when you don't like/hate HTML and Javascript).
CEO at: - Rafaga Systems - Para Facturas - Modern Components for the moment...
Hehe, talking about irony; cross-compatibility is my reason to use .NET, as the assemblies are binary compatible between systems. I can compile on Windows under VS, copy to USB, and run it under Mono. Some third-party libraries work, some don't (heavy interop etc.) I'm currently developing targetting Ubuntu (desktop), and before that Debian (Raspberry Pi) Java will stay around, and we'll keep seeing new versions. Good to have some competition, and good to have choices.
Bastard Programmer from Hell :suss: if you can't read my code, try converting it here[^]
-
tecgoblin wrote:
I cannot count the number of projects I've seen which have been stack in an obscure minor version of java (as in 1.5.21, and not .22 or later) because one of their libraries breaks if you upgrade.
Well, that's what happen when you use undocumented features, and that happens in every language.
tecgoblin wrote:
I've never seen such a major problem with .NET.
That's because your computer have around 4 versions of the .NET Framework installed and Windows manages (juggles) which one you use behind the scenes. But uninstall the .NET Framework 2.0 and try running an app that targets it in the .NET Framework 4.0 and you will see that Java problems seems like a walk in the park.
tecgoblin wrote:
But I CAN count the number of projects in Java 1.7 I've seen in production. Zero.
If you don't see them, doesn't mean they're not there, but anyway Java 1.7 is pretty young (less than a year), and so i can say the same from projects in production in the .NET Framework 4.0 or 4.5.
CEO at: - Rafaga Systems - Para Facturas - Modern Components for the moment...
RafagaX wrote:
Well, that's what happen when you use undocumented features, and that happens in every language.
I don't refer to undocumented features. In most cases it's a dependency, which, without you knowing it, uses a weird workaround or something that later was considered a security breach and has been patched. It can happen in any community, but it's characteristic of Java projects (due to their size and the fact that you're greatly encouraged to swap official packages for community projects - which has of course it's good side).
RafagaX wrote:
That's because your computer have around 4 versions of the .NET Framework installed and Windows manages (juggles) which one you use behind the scenes.
Actually 3 (1.1, 2.0 and 4.0). There aren't 4 out there. Windows comes with one of them pre-installed and it might download a second one if you need it. I don't see this as a problem. It's almost transparent to the user, and it just works.
RafagaX wrote:
i can say the same from projects in production in the .NET Framework 4.0 or 4.5.
I've worked in both java and c# shops (and in many cases mixed ones) for the last 2 years. I haven't seen a single project approaching release on Java 7 (3/4 actually are still on Java 5), while I am already at my third one on .NET 4 (we even have in beta one in ASP.NET MVC 4, which hit release status a month ago). One of those was a military project. The point was not to say that .NET is actually better at this, but just to refute your points about "stability". Java has managed at the same time to be stagnant as a language for the last 5 years, trying to keep things stable, but in the end there's so little gain by new versions of Java that it's difficult to convince the management that you should put the effort to migrate a project to newest versions.
-
Hehe, talking about irony; cross-compatibility is my reason to use .NET, as the assemblies are binary compatible between systems. I can compile on Windows under VS, copy to USB, and run it under Mono. Some third-party libraries work, some don't (heavy interop etc.) I'm currently developing targetting Ubuntu (desktop), and before that Debian (Raspberry Pi) Java will stay around, and we'll keep seeing new versions. Good to have some competition, and good to have choices.
Bastard Programmer from Hell :suss: if you can't read my code, try converting it here[^]
Eddy Vluggen wrote:
Some third-party libraries work, some don't (heavy interop etc.)
That's why i keep Java for these purposes. :)
Eddy Vluggen wrote:
Good to have some competition, and good to have choices.
I couln't have said it better.
CEO at: - Rafaga Systems - Para Facturas - Modern Components for the moment...
-
RafagaX wrote:
Well, that's what happen when you use undocumented features, and that happens in every language.
I don't refer to undocumented features. In most cases it's a dependency, which, without you knowing it, uses a weird workaround or something that later was considered a security breach and has been patched. It can happen in any community, but it's characteristic of Java projects (due to their size and the fact that you're greatly encouraged to swap official packages for community projects - which has of course it's good side).
RafagaX wrote:
That's because your computer have around 4 versions of the .NET Framework installed and Windows manages (juggles) which one you use behind the scenes.
Actually 3 (1.1, 2.0 and 4.0). There aren't 4 out there. Windows comes with one of them pre-installed and it might download a second one if you need it. I don't see this as a problem. It's almost transparent to the user, and it just works.
RafagaX wrote:
i can say the same from projects in production in the .NET Framework 4.0 or 4.5.
I've worked in both java and c# shops (and in many cases mixed ones) for the last 2 years. I haven't seen a single project approaching release on Java 7 (3/4 actually are still on Java 5), while I am already at my third one on .NET 4 (we even have in beta one in ASP.NET MVC 4, which hit release status a month ago). One of those was a military project. The point was not to say that .NET is actually better at this, but just to refute your points about "stability". Java has managed at the same time to be stagnant as a language for the last 5 years, trying to keep things stable, but in the end there's so little gain by new versions of Java that it's difficult to convince the management that you should put the effort to migrate a project to newest versions.
tecgoblin wrote:
Java has managed at the same time to be stagnant as a language for the last 5 years, trying to keep things stable, but in the end there's so little gain by new versions of Java that it's difficult to convince the management that you should put the effort to migrate a project to newest versions.
Sadly i agree with the fact that Java have evolved very little, and that's why i'm going to the .NET Framework for new projects unless i have no choice (Although some languages that run on top of the JVM seems to be more active than Java itself).
CEO at: - Rafaga Systems - Para Facturas - Modern Components for the moment...
-
Until Java 1.5 & 1.6, Java was a snail, compared with C++, for example. There are tons of sites that show benchmarks. A good upshot of that is that it encouraged people to spend more effort on optimising code.
I wanna be a eunuchs developer! Pass me a bread knife!
Mark Wallace wrote:
Until Java 1.5 & 1.6, Java was a snail, compared with C++, for example. There are tons of sites that show benchmarks.
Fortunately, Java 1.5 came out over 8 years ago. Given comparison sites[^] that show these performance numbers for Java6, perhaps the better question is, with the exception of access to proprietary APIs, why would you use other languages? What are they bringing to the table that Java doesn't supply? And that's for a 6 year old release, which has recently had another major version update with significant improvements to it as well. Note that I come from the server side of the coding world, and I have worked with many different languages over the years. The reason people use java, at least in this realm, is because you can create relatively robust software with greater ease than any of the alternatives. C/C++ would get you potentially better performance/memory utilization, but you would need some very highly skilled devs to obtain that boost, and the development time would be significantly higher. Scripting languages (Ruby, Groovy, PHP, etc) all fail in this arena for many reasons, ranging from poor performance to lack of standard library support to non-existent security to list but the major ones. For those that state that scripting languages allow for faster development - my response is yes - a faster road to crap. scripting languages have their place, the enterprise is not one of those. C# is but a weak (originally proprietary) clone of Java, meant to undermine Java's growing market share at the time, It's an ok language, if you're running on Windows, but I wouldn't run it anywhere else, as Java is both better and better supported there. For those that state you can run compiled C# code from windows directly on *nix, I merely laugh. That may be true for a small subset of code, but certainly not for the general C# windows program. I do understand the irony of posting a reasonable pro-java post on essentially a pro-windows board. I will also state that I've seen even successful projects migrate to Java, but never a Java project migrate to something else. (Again, all in the server world) In the client side, Java has had challenges, but also some n
-
Norm .net wrote:
That may be but apparently it's installed on 1 Billion Devices :)
That may be but apparently it's installed on 1 Billion phones. FTFY.
-
Not bad for the times and for the tasks it was designed for. I don't think I ever put anything in IDENTIFICATION DIVISION except the PROGRAM-ID. The idea that in the CONFIGURATION DIVISION, you could specify source and target computers was an idea before its time. Even for today. Unless there were cross-compilers for every computer on every make of computers, that was useless. By the way, I always thought RPG stood for READ, PRINT, GO BACK; a throwback to its derivation from the wired-program accounting machines such as the IBM 407. :laugh: Some salesman named it Report Program Generator and people bought into that!
Vivic wrote:
The idea that in the CONFIGURATION DIVISION, you could specify source and target computers was an idea before its time. Even for today. Unless there were cross-compilers for every computer on every make of computers, that was useless.
Cross-compilers existed for many computers several decades back. Granted, I don't know when this specification entered the spec, that was before my time :)
-
Hehe, talking about irony; cross-compatibility is my reason to use .NET, as the assemblies are binary compatible between systems. I can compile on Windows under VS, copy to USB, and run it under Mono. Some third-party libraries work, some don't (heavy interop etc.) I'm currently developing targetting Ubuntu (desktop), and before that Debian (Raspberry Pi) Java will stay around, and we'll keep seeing new versions. Good to have some competition, and good to have choices.
Bastard Programmer from Hell :suss: if you can't read my code, try converting it here[^]
-
Most in demand or hardest to find resources? There is a difference...
____________________________________________________________ Be brave little warrior, be VERY brave
Adriaan Davel wrote:
Most in demand or hardest to find resources? There is a difference...
What? First the site documents what they count. Second what exactly do you think that your statement means in terms of the overall general job market, now and in the future?
-
Until Java 1.5 & 1.6, Java was a snail, compared with C++, for example. There are tons of sites that show benchmarks. A good upshot of that is that it encouraged people to spend more effort on optimising code.
I wanna be a eunuchs developer! Pass me a bread knife!
Mark Wallace wrote:
Until Java 1.5 & 1.6, Java was a snail, compared with C++, for example.
And now and before Java existed, requirements, architecture and design were still almost always more important. And if you go back a bit further than that language choice meant nothing because there was no language choice - one used what the machine came with or wrote in assembler.
Mark Wallace wrote:
A good upshot of that is that it encouraged people to spend more effort on optimising code.
The upshot of people understanding where real performance bottlenecks originate, in requirements, architecture and design, is that they look at those before implementing solutions that have no possibility of becoming preformant regardless of profiling without refactoring.
-
Where was dotNet in 1998? Ever hear of MS Java or J-sharp?
Basic history:
MS saw popularity of Java rising.
MS products at the time were VB or else VS C++/MFC
MS tried the embrace, extend, extinguish recipe with Java 1.1,
but Sun sued them over changes and additions MS added to Java
MS stopped their Java implementations at 1.1 as part of a settlement and
agreed to support Sun's applet plugins better in IE.
MS still saw the benefit of the technology, so they switched all of their
Java/VM efforts into dotNET/C# to directly compete with Java.
Look at the original dotNET APIs vs. Java APIs at the time. 1:1 correlation.
Meanwhile, Sun had become too content with the Java 1.2 spec. They thought they
were done!
dotNET caught up to Java and passed it up in terms of functionality.
Sun grudgingly started adding things like generics and enums which they originally
said they would NEVER add.
Thank goodness for the competition or Java 1.2 might have been the last Java version!Reasons for using Java:
It was the best choice in 1998, 1999, etc.
Many Java tools have had hot code replace since 1999. (Huge time savings!)
It is still a good choice today. (Still best for our product)
It is so universal, that there is TONS of free, open Java source out there.
It is multiplatform. (Yes. with no recompilation, it runs on Windows, Mac, Linux)
It was and still is browser deployable.
Silverlight apps are just Java Applets reworked. (Admit it!)
Java Applets will keep working,
but it looks like MS is already trying to kill Silverlight.
Browser deployments of Java can still provide more consistent behavior
cross browser than JavaScript/HTML5.
Java+Eclipse allows for 25,000+ source file recompiles in 10 minutes,
of course, good incremental compiling is
normally subsecond to compile and hot replace
true databases of workspaces/solutions, etc. As far as I can tell,
VS looks like it still scans files for references.
It has been really stable. Code compiled against Java 1.2 12 years ago should still
run fine with 1.7.
If you adopted (and reworked your app) each time MS technology
for database access has changed, how many times would you have done this?NOTE: You should never let any untrusted site run ActiveX, Java, JavaScript, etc. in your browser, EVER! Why did Microsoft have to add the ActiveX kill bits, etc
englebart wrote:
It was the best choice in 1998, 1999, etc.
That is no more true now than it was then. What is true if that developers have preferences. And try to rationalize those subjective choices.
englebart wrote:
Yes. with no recompilation, it runs on Windows, Mac, Linux)
However one would still need to test it. If you take a enterprise application and attempt to run it on Mac after developing solely on windows, without testing on Mac, it will probably fail. And at least around 1.2/3 the 'common' idiom for developing GUIs wouldn't translate either. One could only generally write that if one had already seen the problem before. And if you consider re-compilation a 'problem' then you should probably learn a bit more about managing a code. Or perhaps you were referring to the necessity that you might need to actually write different code. However depending on what you did in Java you could need to do that in Java as well.
englebart wrote:
Java+Eclipse allows for 25,000+ source file recompiles in 10 minutes,
of course, good incremental compiling is
normally subsecond to compile and hot replaceWhich of course has nothing at all to do with choosing a language. If you can't manage compiles in a large project in a reasonable way, regardless of language, then it only demonstrates a lack of experience in creating large projects.
