A week of fprintfs has me wanting to code rust next week

Go is like snakes: you're hatched from an egg and pretty much effective from the get-go. The older you get, the bigger prey you can eat, but otherwise things don't change much since you were hatched. Your species can thrive in almost any environment, you're effective, you have all the tools you need straight out of the egg.
Rust is like humans. There's a huge incubation period, and you're mostly helpless when you're born, but the older you get, the more effective you become with the tools nature graced you with. And you, like Thanos, are inevitable, even if it does mean the death of billions.
Python is like beaver. Everyone has an opinion about you: some think you're cute, some think you're wierd. You're perfectly suited to your environment, but things get awkward outside of your natural habitat - you can function, but not as well as when you're in your comfort zone. And when people encounter you where they're not expecting, they can be unpeasantly surprised, and you can cause them trouble.
C++ is like platypus. You resemble some other more simple, some might say sane, animal, but developed into a sort of frankenstein monster creature made from a jumble of parts and a stinger that, when it kills someone, comes as a shock. Every part of you serves some purpose, even if it seems tacked-on and out of place.
Then there's Node. You are everywhere. You are legion. You fill up ecosystems. People try to defend you, claiming that you serve some purpose in the foodchain, but there's scant evidence. Attempts to eradicate you fail. You often spread deadly disease. You breed, rapidly, persistently, relentlessly. You are widely hated, and yet everwhere.
Edit: typo
- In other words, node = mosquitoes or invasive ant species?
  
  I thought roach myself.
  
  Did I find another Sanderfan in the wild?
- Didn’t it only recently get generics? How was stuff even done before then?
  
  Amen. I couldn't have said it better.
- These are excellent.
  I need to add Perl.
  Perl is a honey bee. You are unassuming and pragmatic. You fill every niche. Your buzzing carries meaning, but only to other bees. In theory, your ecosystem niche is filled by many competing solutions that are more fit to purpose. But somehow we all know in our hearts that if you disappear, all life on the planet will probably die soon after.
  
  May I acquaint you with the Evil Mangler, historically used by GHC to compile Haskell via C. It would go through the assembly gcc generates and rearrange whole blocks and deletes instructions, such as function prologues and epilogues.
- So then I guess C is salamander. Also lays eggs and lives by a pool, but doesn't do anything extra, and is a necessary step before most of the other modern languages.
  COBOL is a coelacanth. To everyone's surprise, they're still out there. We thought they were an old, very extinct example of a non-terrestrial lobe-finned fish, but they actually hung on in some odd environments. They cause massive indigestion to anyone that has to consume them.
  If Node is a mosquito, Javascript itself is another hymenopteran: the yellow jacket wasp. Just as hated, and with a tendency to injure handlers, but widely successful and defended as filling an actual useful role in nature. They build delicate, arguably pretty nests.
  
  I especially enjoyed your COBOL metaphor. Nicely done!
  
  Nobody who has seen a yellow jacket nest in person would argue they're pretty.
- Node: You fill up ~~ecosystems~~ hard drives.
- Node isn't a language though.

- C++ compiler:
  Error: missing ';' on line 69
  Warning: two statements on same tabulation depth after if without curly brackets on line 123. Are you sure you want this?
- Sql errors: there be a syntax error roughly over there I think. Or maybe it's a semantic error somewhere else I'm not entirely sure. Listen man all I can say is that this one comma there definitely has something to do with it probably, and the error is most certainly either to its left or to its right.
  
  JSON parsers are getting me recently. The error is somewhere on or after row 1, char 1. Maybe.
  Possibly it's a BOM issue, or someone used double quotes typed on a Mac keyboard. Good luck.

I would swap Python with C++. Constantly dealing with stupid runtime errors that could’ve been easily captured during compile time.
Did you forget to rename this one use of the variable at the end of the program? Sucks for you, because I won’t tell you about it until after 30 minutes into the execution.
- you need a linter, bro
  when integrated into the editor it'll highlight stupid mistakes as they're typed
  I recommend Ruff for real time checks, and pylint if you need a comprehensive analysis.
  
  sure, but thats just outsourcing the problem.
  
  Yea and C++ is the same thing, you just need to enable all the warnings on clang-tidy
- My brother. That's why you do unit tests.
  
  And lint
  
  But are you even a real programmer if you don’t test in production?
  
  I shouldn’t need to do unit tests for quick one off scripts
  
  What's that?
  /s
- You can solve this with git:
  git gud
  Seriously though, writing a monolith of a function and not testing anything until you run it the first time isn't the way to go. Even with a compiler you're only going to catch syntactical and type issues. No compiler in the world is going to tell you you forgot to store your data in the correct variable, although it or a a linter may have helped you realize you weren't using it anywhere else.
  
  Python was typeless. And it was common to reuse variables with different types of content.
  So you at some point never knew what actually is within the variable you are using.
  Using typing in python solve 95% of your problems of having runtime errors instead of compile errors
- Catching some errors is better than catching no errors. No compiler in any language can protect you from all runtime errors either way, but some are better at it than others.
- Seriously, in what way does the python interpreter protect you?
  
  It doesn't. It carries you by having a module for absolutely everything even shooting yourself in the foot.
- Yeesh. I mean, perl would tell you about that immediately, I'm just saying... :-P
  
  Yeah, but then you have to use perl
- I guess as a C# guy I've never had to deal with an issue like this. Most of the time the exceptions are pretty easy to diagnose unless it's in the UI or in some async function.

Rust: “Oh honey you aren’t ready to compile that yet”
- I love "unimplemented!"
  
  Or its alias, todo!()
- I think your comment embodies Rust more than any I've seen before

C holding a gun: "if you segfault it's your own fault"
- Assembly (Octopus swimming alone since birth): "compiler? what's a compiler"

If you're using C++, why not use streams?
- Yes, fprintff is a C thing.
  
  Well, that means that it's also a C++ thing, but streams are an even slicker concept that aren't a C thing, making higher-level code look nice and shiny - and abstracting away loads of I/O pain points while encapsulating useful features.
  
  *ffprintfff
- I wasn't personally using C++, I was using relatively modern C which has had an homegrown object system added to it.
  
  Then it's not C++. And probably an even bigger mess.

Use streams, or fmt. fprintf is for C. It's like people buying a cheap android phone, then going for an iPhone.
I don't blame you though, C++ carries a lot of baggage. Modern C++ is pretty nice, though, as is Rust.

And there's haskell compiler

C++ and C compilers are much more friendly now a days
- can't wait to use templates and have the compiler spit out a 120 page autobiography

A quick -Werror=format -Werror=format-nonliteral -Werror=format-security will solve all your printf woes.

Why are you using fprintf in C++ anyway?

@stsquad
— Is my program about 1,000 lines complex?
— Yes, sure!
— Here you are my about 1,000 lines of 'printf("Hello, Worldn");'.

The meme will be completely different after writing a few lines of rust for a week 😹

How does Python at all help? I don't understand

- There's no parent at all. Maybe a tiny confused baby sea turtle.

Forgot a semicolon? That's 200 errors
- Example?

Cannot agree with compiler part of cpp. Linker errors on the other hand...

Dew it!

I see you're still wading through the high level morass.

as a non programmer, but someone involved in fields intimately similar in fundamental manners.
Honestly i get the feeling that languages and compilers are going to stop babying the user and go RISC-V at some point.
Who needs complex structures and tons of rules when you can just use a turing machine instead!
- As a non-surgeon I think doing a heart transplant without bypass shouldn't be that hard if you're fast enough. I mean you can cut arteries quickly with bolt cutters right?
  
  depends on how precise those bolt cutters are. Knipex? Yeah probably.
- ???
  
  a language with all the good parts of something like assembly, and without all the bad parts of more modern, complex, and "safe" languages.
  One major rule for designed functionality is simplicity. The second you add another rule, the amount of things that can happen grows immensely. And that only scales worse the farther you go. The simpler something is, the easier it is to be intimately familiar with it. Which is what allows people to make proper use of something.
- You can certainty do this, yet it's not time- (and hence cost-) efficient.
  
  yes, that's the problem though. There's a solution somewhere in there.
- I don't understand. You mean everyone goes back to assembly? I could get on board with that.
  
  think assembly, but without the assembly part.
  All the good parts of shit like assembly without all the bad parts of more involved languages like js. Or god forbid front end development frameworks.