quote:Original post by dmikesellquote:Original post by Arild Finesquote:Original post by dmikesell
Strike two. Still waiting for a serious refutation of what I wrote...
You need to write something serious first. Judging by your history, it seems we are in for a long wait.
Well it was obviously serious enough to get your panties in a wad. You''re just angry because I was right.
quote:Original post by dmikesell
Strike two. Still waiting for a serious refutation of what I wrote...
C++ requires discipline or you''ll write code rife with memory errors and leaks. I''d rather not maintain that kind of code, so I''d prefer that undisciplined programmers uses something else. And in most cases I think they do in fact make the switch to something that will help mask their lack of discipline.
quote:Original post by Aldacronquote:Original post by dmikesell
Strike two. Still waiting for a serious refutation of what I wrote...
C++ requires discipline or you''ll write code rife with memory errors and leaks. I''d rather not maintain that kind of code, so I''d prefer that undisciplined programmers uses something else. And in most cases I think they do in fact make the switch to something that will help mask their lack of discipline.
I''ll bite
Ever heard of dangling references? In a Java application of any significant size these can easily lead to OutOfMemoryExceptions, are difficult to track down, and very easy to create. A very common mistake made by those with little Java experience.
Ever used Java ByteBuffers? People always forget to flip/rewind, or set them to native order. A very common mistake when writing net code or using a library that makes heavy use of NIO buffers such as LWJGL, and hard to track down for someone who doesn''t know what to look for.
I could go on, but my point is that *programming* requires discipline. A language will never take that away. They can give us safety nets, they can help reduce development time/costs, but there will always be a way for us to shoot ourselves in the foot. Besides, there are plenty of language-agnostic things that require constant attention on a team (coding conventions, CVS merges, etc...), any one of which could cause a stall in the project.
Don''t make the mistake of thinking that programming with Java is easy. I''ll argue that programming with C++ is just as easy. What''s difficult in both languages is programming *well*. And that requires time, experience, and discipline.
Quote:1) JIT is hypothetically superior, but in practice remains broadly inferior (especially when compared to advanced static compilation mechanisms like profile-guided optimization)
1.5 client / ASM memtest-1953 stacktest-2403 java memtest-2103 java array-6579 1.5 server /ASM memtest-1862 stacktest-2454 java memtest-60 java array-1462 memtest-1883 stacktest-2413 java memtest-0 java array-1433 All data were in L1 processor cache so no problem with memory access.It took 60 ms to eliminate the loop out. That 1433 ms is interesting as well.Quote:Yes JIT in 1.5.0 is still slow, but so is VC 7.1 compiler.
Quote:I hope you joked in rest of your post.
Quote:Original post by Raghar
There is no comparison between Java and C++.
Quote:For example Java has multipass compiler.
Quote:Code maintaince is much better in Java.
Quote:And so on.
Quote: Most of major quirks of C++ will appear lately when it's late.
Quote:I had problem with that expressivnes, and better library words.
From view of ASM programmer both languages have roughly same expressivnes, but C++ forces programmer to type more. ASM, or and possibly halfcript is more expressive.
