3 ms·
To be fair they did say that when contributing to a shared project they follow the prevailing standard. I don’t see the harm in following this for your own pas
by mberning 3y ago
To be fair they did say that when contributing to a shared project they follow the prevailing standard.
I don’t see the harm in following this for your own passion projects. You aren’t doing it for the world, you’re doing it for yourself.
- ComputerGuru 3y agoI mean to each their own, but in my own experience, I value being able to easily and reliably copy-and-paste code snippets across projects (and I have a million of them, across several evolutions of my own personal coding styles and conventions) or files without worrying about whether the typedefs are in scope, polluting a namespace with possibly conflicting names or macros, etc. I also have often found myself publishing “for my own use only” code as open source later and like to keep things understandable to maybe help teach someone something someday.