@LukasHozda Many of the most talented C developers I know also know other languages.
Expanding your mindset and experiencing different mental models associated with other languages makes you a better programmer.
@RuskiZoomer It's crazy because I'm not even saying anything bad about C or even praising C++ this is somehow worse than the classic pancakes vs waffles twitter drama
@JosephZander@MrCMAnderson Having predicable struct layouts is a requirement for having a stable ABI.
Otherwise a shared library could expect structs ordered one way and the library user could provide it another way.
"churn" is a metric for how frequently code gets changed.
This is usually something you want to minimize as well-written code doesn't need to be changed often.
However, when the requirements change with every prompt, there's only so much you can do to avoid churn.
MIT published the most uncomfortable paper on vibe coding.
They tracked every new app that dropped on the app store, play store and chrome web store after coding agents showed up.
And the findings are brutal.
devs who started using autonomous agents wrote 25.5x more code. commits up 240%. repos touched up 80%. actual releases? +30%.
So like... where's the other 95% going?
In the trash.
After adopting tools claude code, devs wrote 7x more lines and deleted 12.2x more. repos abandoned within 30 days went from 60% to 69%.
and the storefront side is where it gets kinda bleak. new apps launching across the app store, play, chrome web store, sourceforge - roughly doubled since early 2025.
user engagement? didn’t move.
that's the part that messed with me honestly. twice as many apps shipping into the void. nobody downloading more, nobody using more. just... more noise on the shelf.
I’ve been thinking about this bc i felt it myself. i shipped three "projects" last month with claude code and im pretty sure zero humans used any of them.. its so easy to start something now that finishing stopped meaning anything.
writing code was never the real bottleneck. shipping something coherent, reviewing it properly, building a thing anyone wanted - that was.
Likely scenarios:
1. I initially did FILE* f or just int fd with a comment noting this was temporary but I changed it and forgot to remove the comment.
2. Thought maybe I could limit the offset size to save memory
@JosephZander@MrCMAnderson Not in c/c++ unless you use special flags. The size and order is important in my case too since I'm making a shared library that could be used on different systems
@Rbaker923456 In another thread I came to the conclusion that i probably just had the fd at first and put the todo comment to keep track of the position but ended up useing long instead of int or off_t... And then didn't remove the comment
I'm pretty sure any reasonable compiler would optimize this out in nearly every case that matters... Especially if you aren't reading uninitialized variables.
I am not sure I like this C++26 standard change. Makes all existing software slower.
Wasn’t hard to write ={0} when you needed it. Yes, sometimes people wrote bugs by forgetting to initialize their variables, but compilers had pretty good warnings for it.