What if instead of continuous integration we had continuous Disintegration, where you code while listening to The Cure on repeat
I had a job where for whatever reason their codebase that was started in 2010 was mostly assembly
whenever I was upset with them, I would write the most esoteric assembly with zero comments explaining how whatever I was making worked
this is neither an endorsement nor a rebuke of assembly, just my (technically) professional experience with it
Ruby does that (well you use the keyword “end” instead of a bracket) but it fell out of favor before it got as big as python, to my knowledge, because of worse multithreaded performance in comparison (which I think has been fixed) and a bias towards unix systems over windows
I like C# and Visual Studio
this is the right answer for the question, the only thing I would suggest is in step 4, to use realloc instead of doing malloc/memcpy/free cycles, since realloc does all that and will simply extend the allocated space so it can skip the memcpy and free steps if possible, which is a little faster
I dont really see the point of the 2nd line in main, fgets already makes sure to null terminate
Karen-based firewall