file extensions are just noise #18
Replies: 3 comments 2 replies
-
No, you could also be right. JavaScript and TypeScript abbrs are inside the list as direct me effectively as a web dev and I thought they should be included (see past #30 and #32) as they are not only file extensions (like .txt, .doc or .mp4) but programming file extensions (like .html, .css or .py) Disclaimer:
is included as a "normal" file extension but because is 🔴 Not recommended My original thought was that maybe other kinds of programmers like C#, Swift, Rust or Go programmers (areas of programming not related to web dev) wouldn't know js or ts's file extensions (I don't have the minimum idea what Rust or Go's file extensions are they wouldn't stick in my brain even if I learned them simply because I don't care and I'm not using them). I'm leaning towards your idea
Thank you. Just for clarity, I'm not the original author |
Beta Was this translation helpful? Give feedback.
-
nice one, even more impressive. Bit, I've upped the conciseness in my code style through the years and I've seen nothing but improvements. My brain just refuses to read verbose code anymore. I'm a standards person and I can't be doing my own thing, nor expect anyone from my team to stick to my own abbreviations, so this project ticks boxes. Do you need any PR's for anything that's gonna keep the list nice and tidy? Got a todo list I can maybe look at? Needs unit-tests in anything?
yes... I'm with you. Rust is How do you use this? Manually look-up something on the site when you need it? |
Beta Was this translation helpful? Give feedback.
-
Going down the path of including file extensions is going to create a substantial amount of noise for minimal value.
there is a minimal amount of grammatical space available and unnecessarily diluting it with (already well documented) file extensions doesn't make much sense.
I could be wrong. thoughts?
Beta Was this translation helpful? Give feedback.
All reactions