this post was submitted on 26 Jul 2026
29 points (70.4% liked)

Technology

86679 readers
2701 users here now

This is a most excellent place for technology news and articles.

Our Rules

  1. Follow the lemmy.world rules.
  2. Only tech related news or articles.
  3. Be excellent to each other!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, this includes using AI responses and summaries. To ask if your bot can be added please contact a mod.
  9. Check for duplicates before posting, duplicates may be removed
  10. Accounts 7 days and younger will have their posts automatically removed.

Approved Bots

founded 3 years ago
MODERATORS
L3s@lemmy.world
enu@lemmy.world
technopagan@lemmy.world
L4s@lemmy.world
L3s@hackingne.ws
29
Name before type: why 'age int' is better than 'int age' (benhoyt.com)
submitted 3 days ago by lemmydividebyzero@reddthat.com to c/technology@lemmy.world
61 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] MangoCats@feddit.it 1 points 2 days ago (1 children)

I tried to use C++ in 1991 but the Borland Turbo C++ compiler was too buggy, so we used C instead. By 1996 C++ was "ready for primetime" on IBM-compatible PCs (yes, they still called them that, sometimes in 1996) and I switched - for 30 years.

I just spent 10 days building a proof of concept in Python, all the "common wisdom" says that was the fast way to get it done. Now that the prototype is done and the (initial) user feedback is addressed, I'm running a port to something better for lightweight, performant, easy deployment... sadly, C++ isn't even on the radar for potential targets - top 3 candidates were Go, Rust and C#. I can't abide the C# ecosystem, and Rust is just a little too rigid and immature for my tastes, so here we Go... anticipated to take 50% longer to port from Python than the Python took to develop in the first place... we shall see...

[–] elephantium@lemmy.world 0 points 1 day ago (1 children)

I can’t abide the C# ecosystem,

Why not? I like working in C#, so I'm curious what about the ecosystem bothers you.

[–] MangoCats@feddit.it 1 points 1 day ago (1 children)

My perception is one of a treadmill. My fellow developers in C# are much more frequently analyzing migration from one incarnation to the next, updating and installing their license files, evaluating compatibility between versions, and generally spinning their wheels on things not required for getting work done on other platforms.

[–] elephantium@lemmy.world 0 points 1 day ago (1 children)

Yeah, fair. New versions release every year. It's usually good stuff, but it does add some toil to existing codebases.

[–] MangoCats@feddit.it 1 points 1 day ago (1 children)

Back in the day, I was getting a new "99% compatible" DOS version every 6 months (until we transitioned to the PharLap 32 bit extender, got more memory to work with AND stopped the perpetual upgrade treadmill.)

That "99% compatible" thing means: in a 10,000 LOC codebase, you've got 100 things to fix before it works on the new DOS.

I really liked working with Qt from 2006-2024 or so, the only major break was 4-5 (must admit, I never migrated to 6, and nobody forced me to...) and the migration from 4-5 was less painful than a DOS version bump. Also, Qt fully insulated our code from garbage changes happening at lower layers.

[–] elephantium@lemmy.world 1 points 8 hours ago (1 children)

Most of my version-upgrade woes seem comparatively recent, lol

  1. Nullable contexts. It's "easy" to update this with a setting in your project file! ... but it adds warnings to basically every file in the project :( You could break it up by adding a preprocessor directive, but it still added a lot of noise at the time.
  2. File-scoped namespaces. I like this feature for new code, but OUCH does it mess up code reviews when it's an incidental change. I really grew to love Github's "ignore whitespace" setting in the PR diff view because of this.
  3. Migrating from 4.6 to .NET Core. There were a few times when a deploy just ... stopped. It worked on our desktops, and it worked on our test server, but the prod deploy just choked. We might have finally gotten a clue about what was wrong from the event viewer, but it's been a while. I do recall that our usual troubleshooting path was useless in this case!
[–] MangoCats@feddit.it 1 points 6 hours ago

adding a preprocessor directive

Yeah, I've had to do that a few times lately. Really tweaked me when gcc transitioned things from warnings to errors.

Migrating from 4.6 to .NET Core.

Are we on .NET 7? No, only 8 is available here without unreasonable effort to backdate. Does the .NET 7 code run in 8 without mods? Yes, but that doesn't change the hassle of talking endlessly about it.