Re: Java 4 ever
<r><QUOTE author="JohnDavidson"><s>
JohnDavidson said:
</s>
Ganz einfach. Hier zitiere ich einmal meinen ehemaligen Professor. "Je mehr man machen kann, desto mehr muss man auch tun". Es geht einfach darum, dass du mit C++ erstmal viel mehr Fehler machen kannst. Das heißt, man muss auch mehr Arbeit in Qualitätssicherung, etc. stecken. Auch muss man mit C++ am Anfang eines Projektes sehr lowlevel arbeiten. Das beansprucht mehr Zeit. Dynamische Speicherverwaltung ist ein weiteres Thema.<br/>
Natürlich gibt es sehr geile Bibliotheken/APIs wie Qt und Boost. Trotzdem bleibt das Problem mit der Qualitätssicherung/Fehleranalyse und der Speicherverwaltung.<e>
</e></QUOTE>
Wieso muss ich denn bei C++ am Anfang eines Projektes sehr lowlevel arbeiten? Das verstehe ich nicht, bitte erkläre mir das. <br/>
Für mich klingt das eher so wie "wenn du zu schlecht zum Programmieren bist, dann nutzt lieber Java, da machst du schon nicht so viele Fehler". <br/>
<QUOTE><s>
</s>Deshalb ist die Wahl von Java, das auf heutigen Rechnern ausreichend schnell ist, für Anwendungen wie Office die logischere Wahl. Auch besteht hier durch den Garbage Collector die viel höhere Chance, dass man keine Daten bei einem Bufferoverflow verliert <E>
</E> Und entwickele in der Zeit eines Projektes mal einen vernünftigen und effizienten Garbage Collector in C++ <E>
</E> Übrigens kann die Nutzung eines Garbage Collectors tatsächlich schneller sein, als wenn man den Speicher manuell frei räumt. Hab ich in ner Wissenschaftlichen Arbeit gelesen. War sehr interessant ^^<e>
</e></QUOTE>
Java ist leider nicht ausreichend schnell, nichtmal für heutige Rechner. Ich hab leider mit Eclipse angefangen und musste sehr früh feststellen, dass Eclipse mit großen Dateien nicht so gut zurechtkommt. Und das ist gerade mal ein Arbeitstool, nichtmal ein Realzeitprogramm. Und die meisten programme benötigen schon immer schnelle Rechner. Sowas wie <URL url="http://www.internet-schafkopf.de/">http://www.internet-schafkopf.de/</URL> funktioniert leider auch nicht immer auf schnellen Rechner optimal.<br/>
Eine Office Anwendung würde ich logischerweise in C++ als in Java programmieren. Das liegt aber vermutlich auch daran, dass ich in C++ mehr Erfahrungen habe und es für sowas "kleines" sehr viele Bibliotheken gibt. Besonders in der Bildverarbeitung (was ich mal unter einem Office tool abstempel) bist du schon gut dabei, wenn du ein normal großes Bild öffnest und darüber einen Filter laufen lassen willst. Zu großen Matrizen Multiplikationen habe ich bereits schonwas in der vorherigen Seite was geschrieben. <br/>
Wenn es darum geht, nen Studenplan Maker zu machen, nagut, da sehe ich es vielleicht noch ein. Dafür werde ich allerdings ungern die JavaRuntime installieren. Sowas wie der JDownloader ist echt ein tolles Tool, aber reagieren tut das bei klicks alles andere als sofort. Gleiches gilt für ein Java Online Schach Programm, wo dann auch noch eine Spieluhr mitläuft. Bullet kann man da leider vergessen.<br/>
<QUOTE><s>
</s>Ich will C++ nicht schlecht machen, da ich selbst C++ bevorzuge. Aber auch nur weil ich die Geschwindigkeit in meinen Anwendungen benötige. Es ist halt so, das Java nicht aussterben wird. Und gerade nicht jetzt wo Oracle der Chef im Boot ist.<e>
</e></QUOTE>
Außer bei kleinen Tools wüsste ich jetzt spontan nicht, wo Geschwindigkeit keine Rolle spielen würde.<br/>
Beliebter ist allerdings auch C++ oder C als Java. Zumindestens kenn ich wirklich nur sehr sehr sehr wenige Projekte, die in Java geschrieben wurden.</r>
