Microsoft apparently still doesn't quite understand the concept of case-sensitivity in filenames & URLs and just changed github.com/Microsoft to github.com/microsoft, in turn breaking a ton of canonical URLs and references.
It's incredible how shortsighted and oblivious a company of that size can be, really 🙄
@fribbledom so many times I've had to fix case-sensitivity at work by checking out into linux, recommitting & telling everyone "delete that file & pull, trust me on this"
@fribbledom And there you have it, Microsoft strategy in a nutshell.
New tech not ours?::
Embrace, Extend, Take as our own. Damage it so no one else can use it.
That's great for GitHub, but it still breaks build systems, imports, caches, image links and other references, because they are now pointing to a different canonical name.
Some of their own repositories use external services, like TravisCI, which now have broken links & references.
Try to click the build badge on https://github.com/microsoft/vscode-go and see where it takes you.
I'm not sure breaking W3C's standards and various RFCs (3986 as one example) is something I'd call a feature.
Besides that, it's ignoring the case-sensitivity handling git itself imposes, the very tool it builds upon. Keep calling it what you want, it leads to real-world problems and that's what I call a bug.
@eater @fribbledom Github exists in the real world where real people use it, not some fantasy-land where all software doesn’t have bugs or quirks. This is a change that breaks stuff, and they should reverse it, announce it and then do it later if they really need to change it (I don’t see why other for weird esthetic reasons).
@fribbledom I love how quickly celebration turns into "we just broke a lot of things" in that thread.
@fribbledom Reading through the back-and-forth involving the original committer, it seems clear they knew this would make a mess but chose to proceed anyway.
Odd decision. 🤔
That's part of the problem, as it still changes the canonical name of everything within that namespace: build systems, caches, image references and a bunch of other things will break - as they treat URLs case-sensitively as various RFCs and the W3C suggest.
I guess Microsoft is just learning that lesson now.
@fribbledom I guess I'm just confused why that will happen, since it's not a re-writing case insensitivity. Like, an example of an actual situation where this would cause a problem.
I see why it's potentially an issue but I'm having trouble wrapping my head around the actual impact.
Just a few examples:
Many projects link their GitHub namespace with other services like CIs, Linters, Test Badges, Doc Generators and so on. They usually treat URLs case-sensitively, which now leads to broken references. Try to click the build badge on one of their own projects, and see where it takes you: https://github.com/microsoft/vscode-go
Some build systems will fail as they check out dependencies including the full canonical namespace, and now can't find the uppercase version in the filesystem.
No need to apologize, I never feel bothered to respond to sensible, intelligent questions!
It also clearly isn't super obvious this would lead to issues, which is why Microsoft probably ended up in this situation to begin with.
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!