C++ or Java?
>>53486039
neither
python
C#
I like c, but the way c++ handles objects by making out of structure and hiding the details behind a different interface bugs me
>>53486039
C++ if you enjoy doing things the hard way.
Java for easy portability.
Python if you hate your end user.
>>53486150
I think you're just lazy
keep using your babby language
>>53486039
> Java
>>53486039
meth
C# is the best
OP, you should state for what purpose. If you are wondering which of the two to learn, it's not that much of a big deal which you. The main point is to learn programming, after which you can easily switch between languages. But of the two, pick C++ if you are heterosexual.
>>53486166
No one making anything in Python hates the end user more than if they made it in Java. Both require additional software (interpreter or JVM respectively) either already installed or packed into binaries shipping with the program.
Btw, does Java still shill ask toolbar in its updater for windows (topic was end users here, so no >windows)?
C++
Java is slower and doesn't have operator overloads.
Fucking garbage.
>>53486039
Taytay is a whore.
>>53486039
Rust > C++11 > Java > C#
Lua > Python
PostgreSQL > any other SQL
Java for general purpose or multiple platform.
C++ if you know exactly what you want down to the finest detail.
>>53486039
Macro assembly
C
>>53486696
This. Why aren't more people on /g/ learning the superior Rust language?
>>53487478
Rust is superior language, but it's heavily under development and still lacks small things like specifying byte alignment, arbitrary-sized integers etc. and the standard library is still poor. However all the nice features and whole "safe" design makes it into the best in drivers, memory/speed efficient programs and server applications.
>>53486039
She codes in ruby btw.
I prefer C++, even when I'm not doing low level things.
I'm just used to it, and I despise Java.
>>53486039
C++ for OS apps. Java for web apps.
>>53488310
>>53486587
basement dweller confirmed
>>53487733
The "safety" can actually be a hindrance to performance, because often unsafe things are faster because they are correct even though they can't be necessarily proven correct.
Obviously this hindrance is negligible compared to stuff like GC, and it's often worth the safety. But C will _always_ be faster (although that's not necessarily a good thing?)
C#.
It's java but not a steaming pile of legacy nightmares.
>>53488418
>citation needed
>>53488409
>Java
feels good anon
feels good
>>53488259
she doesn't code at all btw.
>>53488498
stfu code monkey
>>53488390
Actually run-time checks are disabled in Release mode, so accessing vectors, memory slices etc. is preformed at native speed. What I was rather talking about are the compile-time checks such as lifetimes, ownership etc. These things doesn't have any performance penalty and are very useful once you understand best practices in writing Rust code.
Also Rust can be as fast as C. The difference might be just in how good given compilator is, but there is no C code that can't be written Rust with the same performance and vice versa. (Without extreme cases like uint128_t which is optimized in asm by GCC, so pure Rust code can never be close to it.)
>>53486039
Both plus C.