Slash Boxes

SoylentNews is people

SoylentNews is powered by your submissions, so send in your scoop. Only 9 submissions in the queue.
posted by Fnord666 on Friday March 24 2017, @06:49PM   Printer-friendly
from the didn't-need-those-folders-anyway dept.

in with a story on Robert Elder Software blog entitled Silently Corrupting an Eclipse Workspace: The Ultimate Prank:

Next time your co-worker asks:

"What's the best way to back up my Eclipse workspace on Windows?"

you can tell them "Just right-click on it and select 'Send to Compressed (zipped) folder' and save the zip file". Unbeknownst to them, you just pulled the ultimate prank by telling them to make a corrupted backup!

          What your friend probably doesn't realize is that the Windows 'Send to Compressed (zipped) folder' utility has a mandatory optional feature to automatically not include certain folders in the archive without telling you. This is a great feature because it demonstrates the excellent sense of humour that the authors of Microsoft Windows have. This feature was no doubt included to allow you to play a variety of hilarious pranks on others by causing them lose data, only to find out about it years later when they want to open the archive and recover it.

The blog post goes on to identify other idiosyncrasies with how Windows mishandles directories whose names start with a period and/or contain Unicode characters.

Reasons you haven't switched to Linux (cont.):

  • 3. Windows has superior development tools.

What other issues have you found with how Windows handles filenames?

Original Submission

This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 0) by Anonymous Coward on Saturday March 25 2017, @06:20AM (2 children)

    by Anonymous Coward on Saturday March 25 2017, @06:20AM (#484042)

    > "Title" is different than the file "title" or the file "TITLE".

    But unless you have taken the red pill and only see hex codes, these are all the same word. Capitalization hints at emphasis, its use as a name or title, or the beginning of a sentence. It doesn't change the word itself.

    Case sensitivity is obnoxious for real word end user use. A user may see their file named "Title" right in front of them, but when they type "title" to load it, Unix-ish OSes will stick their nerdy dick noses in the air and say "I can't find that file, I have noooo idea what you are talking about".

    And who in the real world would file "iPhone" after "Zenith"? Nobody.

    I'm sure some jackass will come along and talk about how they help jack off a horse. But "Jack" and "jack" are the same word. In this case the word "jack" is being used as a name (oh, and with punctuation). It is easy to think of it as a new word since you are now thinking of a person instead of a jack or jacking. But capitalizing a word does not create a new word. If I create a paper file in my filing cabinet about how these people don't know jack, I'll title it "Jack". Same word, but now part of a title. Actually, my hand writing sucks so I would probably label it JACK, and any human could find that file if I asked for it.

  • (Score: -1, Troll) by Anonymous Coward on Saturday March 25 2017, @08:16AM

    by Anonymous Coward on Saturday March 25 2017, @08:16AM (#484061)

    Normies oppose men taking cute female children as brides too.

  • (Score: 0) by Anonymous Coward on Monday March 27 2017, @08:44AM

    by Anonymous Coward on Monday March 27 2017, @08:44AM (#484553)

    > But "Jack" and "jack" are the same word.

    But JACK (JACK Audio Connection Kit, i.e. an acronym) and Jack/jack are not the same word. Also, WINE (for running Win32 stuff) is not the same as wine (alcohol stuff). This is true for any "wordy" acronyms).

    /home/user/JACK (source code for JACK)
    /home/user/Jack (files relating to relative Jack)
    /home/user/jack (no explanation needed)