Programming

24348 readers

309 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 2 years ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

UlrikHD@programming.dev

Software taketh away faster than hardware giveth: Why C++ programmers keep growing fast despite competition, safety, and AI (herbsutter.com)

submitted 1 week ago* (last edited 1 week ago) by HaraldvonBlauzahn@feddit.org to c/programming@programming.dev

24 comments fedilink hide all child comments

To put C++’s growth in context:

Compared to all languages: There are now more C++ developers than the #1 language had just four years ago. Compared to Rust: Each of C++, Python, and Java just added about as many developers in one year as there are Rust total developers in the world.

Whoa. That are some carefully selected numbers. It is like saying that I am earning much better money than my 16-year-old nephew (who just finished school), and that, because my job is installing and servicing coal stoves and coal stoves are still used in large part of the country, the coal stove industry is in a totally healthy state.

Hmm. Sounds like C++ is losing ground to Rust - which is much younger - fast.

Especially considering that according to the Stack Overflow surveys, young programmers tend to get into C++, but experienced developers clearly prefer Rust.

Of course, C++ isn't going to dissppear. It will continue to be used for a long time, especially in old, mature code bases. But the same is true for COBOL. And very few new projects use COBOL. In the same way as some scholars and archeologists need to know Latin, but very few publish research or write new books in Latin - even if it was the language of science just a couple hundred years ago.

you are viewing a single comment's thread
view the rest of the comments

[–] squaresinger@lemmy.world 14 points 1 week ago (1 children)

A FE dev usually has JS/TS, (S)CSS, bash (for tooling scripting), often some kind of templating language, sometimes a separate language for tests (e.g. Java/Python+Selenium).

A BE dev stack that I've had at a few jobs so far: Java + Kotlin as the main dev languages, Groovy+Spock for tests, a templating language for emails, bash for tooling scripting, that abysmal templating language that helm charts use, SQL, Elastic, plus a few random single-purpose languages you need for some random tool in the stack.

If you do full-stack, add both together. And then add languages you need for hobby work.

On a regular day I easily hit half a dozen languages at least briefly. Maybe not as a junior dev, but after a few years in the industry, that's not uncommon.

Unless of course you are a C# or Swift dev, then it's totally possible to stay within your singular language-specific bubble for your whole carreer.

[–] ulterno@programming.dev 1 points 1 week ago (2 children)

I do C++. And mostly, there are 2 languages daily.

C++ with QML, when doing GUI
C++ with JSON for DB related stuff
XML for many other things
XML with CSS for UI, but here, the XML part is mostly offloaded to a GUI toool.
A few times, all 3 happen at the same time, but mostly it's 2.

Unless you are including CMake, qmake and Unix Makefiles of course, but that's not an everyday thing either.

[–] HaraldvonBlauzahn@feddit.org 2 points 5 days ago

Same experience here, with 20 years of experience in the industrial / embedded field.

[–] squaresinger@lemmy.world 3 points 6 days ago (1 children)

Tbh, I would classify everything you do regularly at work as your daily work.

The point remains the same: You need to know all these languages. You cannot say "I'm just doing DB stuff today, so I can totally forget QML and relearn it tomorrow when I have a GUI ticket."

[–] ulterno@programming.dev 0 points 5 days ago

Well, I guess that's one way to put it.
But in that case, I would have 3 years of Python experience, which was <5 hours.