3 ms·
Reading this and your other comments I have two very conflicting vibes that I: 1. Hard disagree on the idea of multiple styles in a single codebase and think b
by benrutter 3y ago
Reading this and your other comments I have two very conflicting vibes that I:
1. Hard disagree on the idea of multiple styles in a single codebase and think being able to identify writers of code by style rather than version control sounds like madness incarnate.
2. Massively want to read a blog post or something from you about your ideas on code style. Sounds like you have some pretty valid and well thought out ideas justying a philosophy of code style I've never heard supported before (I think normally disparate code styles in a code base would get interpreted as a code smell rather than a positive)
- Pannoniae 3y agoHi! I don't have a website or a blogpost or anything, to be honest. If you want to chat about it, I'm happy to - my Discord is on my profile, my email is prisznyak.zsombor@gmail.com , or if you want to communicate with some other platform, let me know.
- arein3 3y agoBetter edit the comment and remove the email, as it can be scanned by crawlers and added to a spam list.
- fireflash38 3y agoImo, just sounds like someone mad that others can't recognize their "style" when reading code that's been through a formatter. Code is not just for style. You get no points for fancy spacing. You get no money for having being a "that guy who likes to format his args weirdly".
- Pannoniae 3y agoIf style didn't matter at all, we'd be writing assembly or bytecode. But we don't, because code is written for humans most importantly. Reducing the code down to basically the AST makes it lose important semantic meaning; which defeats the purpose of high-level languages.