Hacker News Reader

Comment by nivla | Hacker News Reader

Ya that I too agree with this, pretty much all applications can now deal with \n just fine. Having CR LF (2 Bytes) is not only wasting storage space but also wasting bandwidth when transmitting.

While at it, I also wish if Linux distros could get done with case sensitiveness in filenames. Is there any advantage to allowing both Filename.ext and filename.ext? The only time I seen this is when a malware is trying to stay hidden. Also some naming conventions would be nice, when you can have any character including '/' and '.' as a filename, it gets annoying to deal with them in a cli.

View on HN

> Is there any advantage to allowing both Filename.ext and filename.ext?

Sorting by ascii order put capitalized files to the top of the list. Exactly where you should look for important stuff like README and Makefile.

Case preservation without case sensitivity is just dumb. Why bother, because it's pretty? Also, what's up with spaces in filenames? And furthermore, what are all these kids doing on my lawn?

> Also, what's up with spaces in filenames?

What's_up_with_spaces_at_all? Let's_just_join_sentences_with_underscores_for_clarity.

iPreferCamelCase

kebab-case-is-better

> not only wasting storage space but also wasting bandwidth when transmitting

Such an utterly minuscule amount though (especially in the modern times when storage and bandwidth are cheap and ubiquitous), I think you typing that sentence has wasted more storage and bandwidth.

I think a better reason is to avoid issues when working with code files across systems and version control. This actually causes major annoyance.

>Such an utterly minuscule amount though

Sent a bazillion and one times all day, every day. I'm sure it adds up.

And it's still minuscule, even added up, even a billion times over.

My point is that there's no shortage of digital storage space and bandwidth is only getting better. And if CRLF does cause a shortage of storage and bandwidth, I'm sure MS would address it.

It's not a Linux distro thing, all Linux, BSD, Solaris, etc systems are case sensitive because it's the 21st century.

The only widely used file system without case sensitivity is HFS[1]. NTFS to its credit is case sensitive, but Win32 is not, for legacy reasons (same reason as why MAX_PATH still plagues Windows).

[1]: https://en.wikipedia.org/wiki/Comparison_of_file_systems#Fea...

And if you actually go out of your way to try and use the case sensitive HFS+ on a Mac, you have a pretty good chance of getting tripped up by user space software that doesn't like it, like Photoshop[1].

[1] https://helpx.adobe.com/creative-suite/kb/error-case-sensiti...

ZFS supports being case-insensitive.

Reply on news.ycombinator.com