3 ms·
Typical "early-in-carrier" thinking. Copying implementation is totally correct move here. All projects mentioned should have forked stdio and added their hacks
by Tractor8626 1y ago
Typical "early-in-carrier" thinking. Copying implementation is totally correct move here.
All projects mentioned should have forked stdio and added their hacks/optimisations/functionality to that.
They were just too lazy. Can't blame them though. Writing C code is torture after all. One should cut all the corners they could.
- ars 1y ago> Typical "early-in-carrier" thinking. Other way around. When I first started I thought these access restrictions were a great idea. Make sure, I, and other, only program "correctly". When I got more mature I found how often they are impediments, and how little they actually help. I don't want someone else protecting me from myself. I just don't want that, no matter how well intentioned.
- Tractor8626 1y agoWhat I meant are "avoid copy paste at all cost" and "I'm center of the world. What I want is the only thing that matters"-thinking. About access restrictions. We have two nice examples here 1. Stdio devs can't freely make modifications because someone's code depends on private implementation details 2. And yours example. You tried to do wrong thing and those access restriction made you suffer and do the right thing. Works as intended I'd say.