Live data from Hacker News

Should we stop writing functions? (C++)

foonathan.net

1–10 of 44 posts

Re: Should we stop writing functions? (C++)

#2
This kind of post is why I do not understand C++ programmers whatsoever. It's basically a demonstration of the absurd amount of time C++ takes away from you by being the moldy pile of shit that it is. You want better compiler checks and less freedom? Great, me too. Can we please shut the fuck up and use a language that actually supports that?

Re: Should we stop writing functions? (C++)

#3

This kind of post is why I do not understand C++ programmers whatsoever. It's basically a demonstration of the absurd amount of time C++ takes away from you by being the moldy pile of shit that it is. You want better compiler checks and less freedom? Great, me too. Can we please shut the fuck up and use a language that actually supports that?

It simply has too many upsides and is way too popular to be replaced with either

- a simpler language that does less

- a less popular language

- a more verbose / restrictive language

If you want people to switch to something better, make something better. Its not enough to simply call out the issues (which is valid, but not useful anymore), and it entirely dismisses that replacement languages like D (small, less active ecosystem) and Rust (hugely verbose and equally bloated) do not actually service the entire range of C++ users.

If all the other compilers and languages were THAT much better, they would be used.

For a lot of apps, Rust has been that replacement, but not for all domains C++ is used in.

Why do people still use telephones when calling via whatsapp, telegram, element or discord exists? Why do people still drive shitty motorbikes when electric cars exist? Why do people still write by hand when you can type instead?

Because the replacement is not a complete replacement and does not actually work better for everyone.

Re: Should we stop writing functions? (C++)

#4
You look throught the positives and you start to go yeah, yeah! But then on the downsides. Ugh, it will make debugging even more ugly? Debugging considerations are one of the last things people tend to think about when 'architecting'.

Re: Should we stop writing functions? (C++)

#5
post #4

You look throught the positives and you start to go yeah, yeah! But then on the downsides. Ugh, it will make debugging even more ugly? Debugging considerations are one of the last things people tend to think about when 'architecting'.

I always push back on decisions that have benefits with reduced debugability. It's rarely worth the hassle to take on a "more performant" or easier to develop tool if devs can't easily figure out what's wrong with it. Especially in a big company where people move around, and tend not to be familiar with tools...

Re: Should we stop writing functions? (C++)

#7

This kind of post is why I do not understand C++ programmers whatsoever. It's basically a demonstration of the absurd amount of time C++ takes away from you by being the moldy pile of shit that it is. You want better compiler checks and less freedom? Great, me too. Can we please shut the fuck up and use a language that actually supports that?

> This kind of post is why I do not understand C++ programmers whatsoever. It's basically a demonstration of the absurd amount of time C++ takes away from you by being the moldy pile of shit that it is.

What? Exactly what led you to think that nonsense? A random blog post of someone misusing lambda expressions?

There are plenty of things in C++ to criticize, but a) you are not actually criticising anything at all and instead spewed just noise b) misusing a feature is not a problem of C++.

Re: Should we stop writing functions? (C++)

#8

Its important to note the article was published on April 1st.

> Its important to note the article was published on April 1st.

Haters don't waste time trying to understand what is before them. They just see a superficial opportunity to unleash hate and just go for it, logic be damned.

Post reply on HN