Subnostr

i bring it back to Go because they designed it right from 40 years of experience running dev projects, unlike all the rest of these idiots that did 5 years and love to pander to irrelevant obsessions

hell, i remember C++ coming out when i was 15 and i thought it seemed cool with those pipe operators and honestly, nobody uses them, but you look at the code and it's so overflowing with excessive descriptive object specs and template this and fuck off... man, i remember dealing with boost back in the day... zero guarantees that different minor versions would even compile... 1.58, not 1.59, or death!

objects are shit, they just make slow compilation and confusing notation, static analysis doesn't work and the compiler uses 12gb of memory to compile. fuck that

MichaelJ 1y ago

Hey, watch it, I'm working on a C++ project right now! 🤣

I definitely see the complexity you're referring to. However, I wanted to learn C++ better, and I've found it a valuable experience so far.

Maybe next I'll do everything in C lol.

Reply to this note

Please Login to reply.

Discussion

ᴛʜᴇ ᴅᴇᴀᴛʜ ᴏꜰ ᴍʟᴇᴋᴜ 1y ago

lol, C is almost as bad, at least, the way people write it, fuckin unreadable, and it always seems like everything is declared at least 3 times, like, why????

C is static typed, yeah, there's 4 types of ints, two types of floats, strings that are stupid zero terminated, memory is not typed, really, you can simply say it is whatever you like, and then clobber it at will

insane language, 50 years old, come on man

i bring it back to #golang because it's the most cleanly designed, elegant, simple, easy to read, and sensible language that exists, and it doesn't pander to stupid nonsense obsessions about objects or aspects or "run everywhere" (it does anyway) or dynamic linking or functional, or objects, fuck objects, composition > inheritance... use short, concise names, don't write fucking war and peace in your fucking symbol names