C++ VS Java

- illegal memory access protection
- explicit application's memory quotas
- no pointers
- garbage collector
- verbosity
- easy-to-use debuggers
- ability to create heap/stack dumps at any time w/o killing the app
- no include/import clashes (no need for include guards)
- hot-redeploys (update running code w/o stopping the app)
- cross-platform code
- built-in GUI libraries preserving look'n'feel
- built-in GUI library utilising OS's GUI API
- ability to use multiple languages for the application (java, kotlin, groovy, javascript, C, C++ (who said it can't use inline ASM, pointers, etc...?), etc.)
- ... shall I continue?

P.S. I like pointers. I like pointers' math. But it's also a very good place for mistakes to happen and fuck things over

"No int to bool" is a problem now?

Single inheritance is a good thing.

Well I mean you don't really need pointers when you have ｒｅｆｅｒｅｎｃｅ ｔｙｐｅｓ

"No int to bool converter"
Praise the God!

@netikras thank you

@J4s0n what for? :)

@netikras pointing it out

I chuckle with "single inheritance" and "no int to bool"

And don't get me started with "only oop"

I really dig cpp, pointer arithmetic is cool. But if I need to do shit like that I already know I ain't using Java. Most of these retarded arguments would work on many languages btw, not just Java. Can't make a comparison between two tools used at incredibly different things.

Single inheritance? What's an interface?

@AlgoRythm shhhhh don't tell them. Patterns and code architecture is somewhat difficult for the standard makemancppdev

All these statements seem like good features