Timeline for Should we avoid language features that C++ has but Java doesn't?
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 28, 2016 at 19:03 | comment | added | Jerry Coffin | @SebastianRedl: change "Java has features" to "Java has mistakes" (and likewise, "Java's other features" to "Java's other mistakes", "Java-exclusive features" to "Java-exclusive mistakes", etc.), and you're pretty close correcting things. :-) | |
| Jan 27, 2016 at 17:05 | comment | added | DevSolar | @SebastianRedl: The first two paragraphs could be interpreted that way. On second reading, that might have been me. (I know both C++ and Java, and despise the latter, so call it personal bias.) +1 and we're good? ;-) | |
| Jan 27, 2016 at 16:47 | comment | added | Sebastian Redl | @DevSolar How exactly did I give the impression that Java is more advanced? I need to know so I can fix it. | |
| Jan 27, 2016 at 15:20 | comment | added | DevSolar |
I would upvote this answer for being in the right track ("don't do it"), but I cannot stand the basic premise that Java is somehow "more advanced" than C++. C++ does not need a garbage collector or a single-root object hierarchy, the same way Java does not need... err... sorry I don't know how to finish the sentence, because I miss deterministic destructors in Java, and finally isn't a replacement for them. The two languages are just fundamentally different.
|
|
| Jan 27, 2016 at 5:40 | comment | added | bcrist | "Java doesn't have stack-allocated objects with deterministic destructors, but has finally blocks and try-with-resources [...] to make up for this lack." Hardly. Deterministic destruction is not important just for exception safety and to hide resource cleanup, it also moves the responsibility for managing resources from the user of a class to the implementor. | |
| Jan 25, 2016 at 15:44 | comment | added | biziclop | @PatriciaShanahan Never mind features, even variable/function declaration and naming idioms make a huge difference in readability. | |
| Jan 25, 2016 at 14:48 | comment | added | Patricia Shanahan | Beyond the choice of features, there is the matter of style and idiom. Programs are generally easier to read and maintain if they use the normal idioms for the language in which they were written. Even if one could write a portion of a C++ program using only Java-like features, the result would be strange, stilted C++. | |
| Jan 25, 2016 at 13:44 | comment | added | Quentin |
Java's Object is pretty much a void* for most uses -- Still, yuck.
|
|
| Jan 25, 2016 at 13:36 | comment | added | Jan Hudec | Note that C++ does not have finally blocks, but it has RAII, which is much better for most cases. And, again, different. | |
| Jan 25, 2016 at 13:36 | comment | added | Jan Hudec | Seasoned C++ veterans usually reject Google coding guidelines. Modern C++ is vastly better exactly because it uses those features. Yes, it makes it even more different. | |
| Jan 25, 2016 at 10:24 | history | answered | Sebastian Redl | CC BY-SA 3.0 |