c++

No. Now fuck off.

>>62056813
only when C++++ comes out

>>62056813
>WIll c++ ever die?
not without pajeet

No. It's like water.

Why have there been so many "when will C++ die"/"what language will replace C++?" threads lately?

If you truly hate it but want performance use any of the "C++ replacement" languages already out there: D, Rust, etc..

If you have to use it at work, you're gonna have to either deal with it or get a new job.

If none of the above satisfies you, get a new career/hobby.

>>62056860
>C++++
That's C#, friend. Though it's more a replacement for Java.

File: 20.jpg (118KB, 728x403px) Image search: [Google]

118KB, 728x403px

>>62057297
>C#,

Only when JS will have pointers

>>62056813
Never. C++17 is out and C++20 is already in the proposal phase.

It's here to stay.

>>62057297
>C#
>>>/trash/

>>62056813
No, they will keep injecting new features against its will every couple of years to keep its position.

When I create C^

>>62058439
>c xor
>you WHAT

>>62056813
c++ is a fucking mess 10000 tons of ways for doing the same crap causing pajeet copy paste every where its a crap ecmascript is more stable than that shit.

Honestly, the only change C++ needs is common pronunciation.
"See plus pluss" is too long for a programming language name.
"See Incremented," shortened to "See Inc," shortened to "sink" would solve 200% of my problems.

>>62059206
CanCerous

>>62056813
It will never die because it's the most powerful programming language in the world.

>>62058439
looking forward to it

>>62057297
>C#

>C++
> ++

why use c++ when theres javascript and html

File: c#.jpg (19KB, 705x523px) Image search: [Google]

19KB, 705x523px

>>62057297
>>62058392
>>62057655
>>62061115

>>62056820
fpbp

>>62058427
/thread

>>62063090
C++ compilers generally produce code that runs faster.

>>62056860
Wouldn't it be C += 2? Cause C++ was basically supposed to mean C incremented.

>>62064069
no shit sherlock?

>>62056860
C++ is not an lvalue

>>62064069
>>62056860
unary increment does not stack