dayvster

I appreciate you pointing that out, you’re right that this post is very much colored by my own experience. I don’t mean to suggest curiosity or hacker culture is gone entirely, more that in my circles it feels a lot harder to find than it used to.

I’m genuinely glad to hear your perspective though it’s encouraging if you’re seeing the opposite. Maybe the truth is that the spirit is still alive, just spread out in different communities, projects, or corners of the internet than where I tend to hang out. But sadly I'm just not seeing it.

Curiosity is key at least to me if you can find something that sparks your curiosity ambition will always follow.

Hah that's a cool and creative exercise. Love the writing style as well

It's a real shame how software that starts out really well, always adopts horrible and unreasonable monetization tactics once adoption is high enough

From tinkerers to metric seekers: How the shift in developer culture is impacting innovation and creativity.

Oh thanks for the tip, appreciate it.

I see it can even do file previews with kitty which is perfect as I already use kitty as my default terminal.

My only issue with it is that it does not come with vim keybindings by default, I love to have consistent keybindings across my system / TUI tools

I wouldn't necessarily put it like that no. I'd say all languages have features that fit certain situations but should be avoided in other situations.

It's like a well equiped workshop, just because you have access to a chainsaw but do not need to use it to build a table does not mean it's a bad workshop.

C is very barebones, languages like C++. C#, Rust and so on are not. Just because you don't need all of it's features does not make those languages inherently bad.

Great question or in this case counter-counter point though.

Excellent question, I guess it depends on the team mostly how they define which features they need and which are better avoided.

As for why not just go for C. You can write C++ fully as if it were C, you can not ever turn C into C++

This is true and I will concede this point. Appreciate your feedback!

However if I may raise my counter point I like to have a rule that C++ should be written mostly as if you were writing C as much as possible until you need some of it's additional features and complexities.

Problem is when somebody on the team does not share this view though, that much is true :)

Author of the article here.

Really appreciate and value everyone's feedback on this.

I can not overstate my excitement that my blog post has generated this much discussion and debate.

Hi author of the article here.

I've been a software developer for nearly 2 decades at this point, contributed to several rewrites and oversaw several rewrites of legacy software.

From my experience I can assure you that rewriting a legacy codebase to modern C++ will yield a better and safer codebase overall.

There are multiple factors that contribute to this, such one of which is what I reffer to as "lessons learnt" if you have a stable team of developers maintaining a legacy codebase they will know where the problematic areas are and will be able to avoid re-creating them in a rewrite.

An additonal factor to consider is that a lot of legacy C++ codebases can not be upgraded to use modern language features like smart pointers. The value smart pointers provide in a full rewrite can not be overstated.

Then there's also the factor that is a bit anecdotal which is I find that there are less C++ devs in general as there was 15 years ago, but those that stayed / survived are generally better and more experienced with very few enthusiastic juniors coming in.

I'm sorry you did not enjoy the article though, but thank you for giving it your time and reading it that part I really appreciate.