Bill and Ted and Cartman's Maccellent Adventure
-
i have some installations on EXT3 due to their age, a fair few on EXT4, of course every install has a small EXT2 boot partition, and some systems have some REISERFS partitions, though those are getting phased out slowly.
-
if you're going to fix it at some point you have to rip the bandaid off.
You're asking Microsoft to break an unknown number of people's work flow so they can gain the ability to create a file they've never been able to create, lo these thirty years. You're starting at at least -200 points.
-
some systems have some REISERFS partitions, though those are getting phased out slowly.
Man, murder your wife and everyone wants to stop using your software.
-
if you're going to fix it at some point you have to rip the bandaid off.
If people upgrade to newer Windows and shit breaks, Microsoft gets the blame, no matter how good the change was. So they're not going to change it, because they care more about people upgrading.
And it's a really no-priority thing that nobody remembers about most of the time, too.
-
@accalia said:
if you're going to fix it at some point you have to rip the bandaid off.
You're asking Microsoft to break an unknown number of people's work flow so they can gain the ability to create a file they've never been able to create, lo these thirty years. You're starting at at least -200 points.
Indeed. Plus, I'm not really seeing an actual feature gain for an enduser - I mean, how often do you actually need to create two files named alike, save for one being capitalized, the other not?
-
I mean, how often do you actually need to create two files named alike, save for one being capitalized, the other not?
1.2k helpdesk tickets on variations of the theme of "i want my windows filesystem to be case sensitive because " in our JIRA instance.
that's about 10 tickets a month.
of course our salespeople are all special snowflakes
No, i will not pull this intricate data report that you want today when you knew about the need months ago. you should have told me when you found out.
-
1.2k helpdesk tickets on variations of the theme of "i want my windows filesystem to be case sensitive because " in our JIRA instance.
I was talking about "need" in the sense of "actual, rational and reality-based need", not "I'm a moron who needs a map, GPS and two guides two find his own ass with two hands and a shovel."
-
I was talking about "need" in the sense of "actual, rational and reality-based need"
i need case senitive file systems because i collaborate with people who not only use them but also use the case sensitivity feature in their folder structure.
i also need a case preserving (at minimum) filesystem because of the stupid backup software at work treating certain special folder names (case sensitive) in a special "i'll fuck up the backup, but i won't tell you this because fuck you" sort of way. but that's a different debate.
-
i need case senitive file systems because i collaborate with people who not only use them but also use the case sensitivity feature in their folder structure.
That's not a reason I was talking about either. That's a
-
That's not a reason I was talking about either.
it's a"actual, rational and reality-based need",
for me, not so much for him.for him it is indeed a
-
that's about 10 tickets a month.
Then you haven't done a good job of saying "we will never support that; if you don't like it, call Microsoft and complain to them".
-
That may be. I'm still not seeing how having both "ImportantUsers.txt" and "importantUsers.txt" improves the workflow. It would confuse the hell out of me for certain.
Do you know what twisted logic lead to this fuck-up?
-
use the case sensitivity feature in their folder structure.
"Well, shame on them" was my first thought, but really, they should be trained not to do that.
-
Do you know what twisted logic lead to this fuck-up?
I have a coworker who has 4 instances of our software on her computer, for training purposes. I can not get her to understand they're not interchangeable when saving, for example, reports. She'll run one in one instance, and then look for the output file in a random one.
-
Do you know what twisted logic lead to this fuck-up?
that's all i can think of.
Then you haven't done a good job of saying "we will never support that; if you don't like it, call Microsoft and complain to them".
i have told them this, they havent listened.
"Well, shame on them" was my first thought, but really, they should be trained not to do that.
good luck with that. they're 79.
-
they're 79.
Then it won't be a problem for much longer. Hand off dealing with them to a junior and forget about it.
-
what junior?
it's just me and him on this project.
-
She'll run one in one instance, and then look for the output file in a random one.
Status: Recently came across this exact thing. Deployed a new version, which migrated half of the screens to new tables (we're still waiting for approval to use the rest on the new tables as well). Users are using the New application, expecting to find results for what they did in the Old system, despite being explicitly told they couldn't do that (told in words, pictures, meetings, and I even did an animation in PowerPoint!).
-
Then dump the soon to be corpse from the project. They can't be central (or if they are it already is a huge WTF) to it.
-
i have told them this, they havent listened.
"You might as well stop opening bug reports because we're just going to close them without response.
-
@accalia said:
i have told them this, they havent listened.
"You might as well stop opening bug reports because we're just going to close them without response.
and have them complain to their bosses anf VPs that IT is being unresponsive to their business needs?
their bosses and VPs also being nontechnical and for politics reason inclined to believe sales over IT
-
and have them complain to their bosses anf VPs that IT is being unresponsive to their business needs?
Geez. "We have repeatedly responded that due to Microsoft limitations we cannot fulfill your requests." Then you tell management ahead of time that you're being asked to do things you've already said you can't do. Either that or just boilerplate close new requests. "As has been mentioned in ticket #12345, we are unable to fulfill this request due to Microsoft limitations, and are closing this ticket." And then CC management directly.
It's almost like you are avoiding learning how to play this game.
-
It's almost like you are avoiding learning how to play this game.
it's almost like i work with two entire floors of salespoeple who believe IT exists solely for the purpose of doing their job for them, and i want a job tomorrow.
yeah it sucks, but you likely cannot suggest an angle that we haven't tried yet, as evidenced by the fact we have more than one thousand tickets spanning almost ten years.
-
we have more than one thousand tickets spanning almost ten years
Discourse has more pull requests than that in less time. And that's not counting all the forum posts they ban people for.
-
@accalia said:
we have more than one thousand tickets spanning almost ten years
Discourse has more pull requests than that in less time. And that's not counting all the forum posts they ban people for.
i meant issues that are about users wanting case sensitive file systems on windows.
-
What about
"Let me ask the computer."
"The computer says no"
?
-
Do you work at Microsoft? Or are you just being asked to support software you didn't make and have no influence over?
-
Do you work at Microsoft?
on Maine
FAT CHANCE!
Or are you just being asked to support software you didn't make and have no influence over?
and having to explain that to people who literally don't want to understand."Let me ask the computer."
most recent attempt at that strategy.... last septembre, on the 15th. official complaint for unprofessional and obstructionist response was on the 18th"The computer says no"
-
"Let me ask the computer
"The computer says FUCK YOU"
-
-
Seriously though, that sucks. Good luck finding somewhere else or something...
-
i meant issues that are about users wanting case sensitive file systems on windows.
Actually, if they're using NTFS they have a case sensitive file system. They just don't have a case sensitive operating system. NOW YOU CAN CLOSE THE TICKETS.
-
Actually, if they're using NTFS they have a case sensitive file system.
technically correct, which is unfortunately not good enough this time.
NOW YOU CAN CLOSE THE TICKETS.
WE DO! THEY KEEP OPENING NEW ONES!
-
The first is that it's nearly impossible to imagine what bit of Steam could break if the filesystem isn't case-sensitive.
Other than remote code execution, I can't think of any way that could be a problem.
-
why would it be a bad thing?
A file system that is case-sensitive is just trolling users.
-
Pictures/CAT scan.jpg Pictures/cat scan.jpg
"Shit, where are the medical records?"
-
yeah it sucks, but you likely cannot suggest an angle that we haven't tried yet
Find a new job. Email all the salesfucktards on last day, "YOU CANNOT DO THAT AND I CAN FINALLY TELL YOU HOW MUCH OF A STUPID SHITHEAD YOU ARE."
-
and having to explain that to people who literally don't want to understand.
"As I have repeatedly told you, we cannot do this. Here are references 1-7, and I've CCed your boss and mine, again, to explain why nobody can do what you want."
At my company I get to/have to occasionally tell customers we can't or won't do things they want.
-
"YOU CANNOT DO THAT AND I CAN FINALLY TELL YOU HOW MUCH OF A STUPID SHITHEAD YOU ARE."
that may be a better plan than my current plan for my last day of employment.
my current plan has a 1 in 3 chance of ending with my incarceration.
-
technically correct, which is unfortunately not good enough this time.
Ticket closed E_CANTFIX. Resolution: "if you can get me a job at Microsoft maybe I can fix this."
-
WE DO! THEY KEEP OPENING NEW ONES!
CLOSED WONTFIX "No change from the last 6 times you asked--we can't do this. Go call Bill Gates."
-
You can also put Steam on a separate partition, if you've got space for one. Use Disk Management to shrink your Windows partition down and use the free space.
Yeah, there was a whole article about making and maintaining a forest of symlinks needed to keep that working.
Reinstall at this early stage is less painful.
-
Bill Gates.
last i checked he no longer even works for microsoft, let alone has any decision making power.
oh, no he's "technology Advisor" for the board.... that's near as makes no detectable difference
-
Yeah, there was a whole article about making and maintaining a forest of symlinks needed to keep that working.
Buh? If you already installed it somewhere, you copy the directory where you want it, delete some files, and run steam.exe again, and it fixes everything. I used it myself to move from my (small) SSD to my (much larger) hard drive. It's easy.
Of course if you're not using Windows, well, there's your problem.
-
last i checked he no longer even works for microsoft, let alone has any decision making power.
That was a joke, you silly fox. Didn't you get it?
-
I can live without Steam, but I can't live without a full unix compatible shell, for work.
The case-insensitive file system preserves case, so
~/Downloads/
has a capital D and you annoyingly can't tab-complete it from~/dow
. However, it doesn't appear to let you have two files that differ only in case. It's the worst of both worlds, but at least you can play Isaac. FWIW I've never run into the problem of not being able to name two files the same, which I like to think is because it's a bad idea and everyone realizes that.
-
I miss copy con file.txt.
I still use it sometimes, most recently on Windows 8 at work.
-
"We have repeatedly responded that due to Microsoft limitations we cannot fulfill your requests."
Too defensive. Do what Microsoft itself does and go full bland: "This behavior is by design."
-
@boomzilla said:
Actually, if they're using NTFS they have a case sensitive file system.
technically correct, which is unfortunately not good enough this time.
NOW YOU CAN CLOSE THE TICKETS.
WE DO! THEY KEEP OPENING NEW ONES!Luckily, NTFS also supports Unicode in filenames. Every time somebody opens a ticket for a filename conflict, all you need to do is find one of the files concerned, rename it using a Cyrillic homoglyph or two, then close the ticket. Job done.
-
A file system that is case-sensitive is just trolling users.
What about case sensitivity of non-Latin character set? And how do you compare the directory names in a file-system search? Would you save a normalized UTF8 representation? What you will end up with, arguably "is probably the worst file-system ever".