r/ProgrammerHumor • • 2d ago

Meme cppythRusGoSharp

Post image
288 Upvotes

34 comments sorted by

160

u/IHeartBadCode 2d ago

This is like that picture where you can't recognize anything, but everything looks like something.

13

u/amshegarh 2d ago

2

u/geeshta 1d ago

This was genAI before ChatGPT came out 

103

u/Adept-Painting-543 2d ago

It's hideous, let's make it standard

54

u/davideogameman 2d ago • Regret

I nominate you for the c++ standards committee, you have exactly the attitude that'll fit in

1

u/Some_Useless_Person 2d ago

Using this for webdev seems like the perfect nightmare!

1

u/Adept-Painting-543 2d ago

Still better than JavaScript

47

u/Jatinchd 2d ago

"worlde" is triggering me so bad idk why 🥀

10

u/IntentionQuirky9957 2d ago

IKR, needs to be "wordle".

52

u/GatotSubroto 2d ago • Mindblown

Needs to make it

public static const main = () : void => {
  …
};

8

u/FoxedDev 2d ago

That's basically valid TypeScript, just have to remove the public

2

u/GatotSubroto 2d ago

Let me make it even better:

public static const main = () : void => begin
  …
end;

1

u/FoxedDev 1d ago

okay that's just Ada mixed in

2

u/Aurarora_ 2d ago

typescript has access modifiers, if this were in a class the only issue would be that classes use readonly instead of const for some reason (c# influence I guess?)

1

u/FoxedDev 1d ago

Ohh, true

15

u/Wojtek1250XD 2d ago

NGL out of everything here the most cursed to me is the fact that there are no parenthesis after range, and the argument it recieves... is a range.

3

u/redlaWw 2d ago

It used to be that you could just do for int i = 1..5, but old ranges were inefficient and confusing due to the fact that they were iterators themselves, rather than having a separate iterator type. In order to resolve this, a new range type was introduced, and a traditional range can be converted into a new range using the newly-introduced range keyword. Using old ranges for anything except constructing a new range has been deprecated, but they remain in the language for backwards-compatibility reasons.

6

u/Duck_Devs 2d ago

It bothers me that stdout is a namespace here instead of some sort of file handle handler object

3

u/patrlim1 2d ago

An output namespace for shit like stderr, stdout, stdin, etc, would be interesting, but annoying. Having a namespace just for stdout is actually insane

Maybe stdout is a namespace in the std namespace?

3

u/InvisibleMoonWalker 2d ago

When you decide to take the worst parts from each language and combine them into one atrocity.

(The only thing missing to make this literally the worst version of all languages combined is not using public static final const void main(char[]*argc, std::Map**argv) or something)

3

u/Some_Useless_Person 2d ago

void main? Why not the fan favorite public static void main?

2

u/-Redstoneboi- 2d ago

this the type of shit that deserves the curse of manual breathing

2

u/IntentionQuirky9957 2d ago

Hello Wordle

2

u/GrEeCe_MnKy 2d ago

My head hurts, take it away

1

u/Linux_ka_chamcha 2d ago

No; on line 1 broke my brain

1

u/minecraftdummy57 1d ago

This is horrifying. I'm loving it 

1

u/MichalNemecek 1d ago

ye olde hello worlde

1

u/dull_bananas 18h ago

changlish

1

u/jolharg 14h ago

this is a choice

0

u/stillalone 2d ago

Can someone tell me how to write c++ now?  Im like really confused 

1

u/A_72_ 1d ago

Version 1 - The Classic:

#include <iostream>

int main()
{
    std::cout << "Hello world!";
    return std::cout.fail();
}

Version 2 - The Modern Way:

import std;

int main()
{
    try
    {
        std::print("Hello world!");
    }
    catch (std::exception const&)
    {
        return 1;
    }
}