3 ms·
It's a great decision if you don't want me to use your language. I'm already a little fed up with the camelCase vs snake_case coding style conventions I'm supp
by tiglionabbit 10y ago
It's a great decision if you don't want me to use your language. I'm already a little fed up with the camelCase vs snake_case coding style conventions I'm supposed to switch between to write an app that uses both Python and JavaScript. I don't need a third convention, especially not one that's enforced by the language and contrary to every other language in existence, as well as my serialization formats.
- deleted 10y ago[deleted]
- owaislone 10y agoWhat would be the alternative? A keyword? `public`? `export`? May be you prefer but a lot of people prefer simple a simple convention over one more keyword.
- tiglionabbit 10y agoI would prefer keywords because then if you change your mind about what should be public you don't have to hunt around for every reference to it and change its name. Or, give me a convention where public stuff looks normal and private stuff looks weird, because then at least my JSON serializer will work. In Python you lead with an underscore to denote privateness. You could use interfaces to communicate privateness. If something isn't exposed in an interface, it can be assumed to be private. Or just don't have your compiler enforce privateness. You don't need it. Plenty of languages get along fine without it.