On a Linux environment? Mind sharing the usage area?
I learned of those files outside the context of programming. When program or file zip packages contained these random ds store files and I looked up what they are.
Turns out, it’s metadata caching for macOS. Irrelevant and does not belong into [distributed or shared] packages.
/edit: It’s been a long time ago. Looking at it again, I guess it adds folder metadata, so it could be useful when distributing to other macOS. But for other OS, it’s noise. Either way, usually it’s not intentionally included.
Case insensitive handling protects end-users from doing “bad” things and confusion.
is exactly the same as programming case sensitivity
Me working on a case insensitive DB collation 🤡🚀🐱🏍
Why would you order lowercase before uppercase?
Let’s put a story point estimation on that. Then we can extrapolate time range and risk.
How’s it going so far?
The solution to this problem. . .
is that they have to create a support ticket with you, that you then put in progress, and you walk them through your documentation, and then log your time spent onto that ticket. (/s)
There’s an alternative to creating too many tickets that only add overhead and then make it harder to get into the project. Creating a good amount of tickets.
I took the OP reference as demand for ticket creation when they don’t make sense and only hinder development through unnecessary overhead. E.g. creating a ticket before a quick analysis, or creating individual tickets when one story/feature ticket would be enough. Or more specifically in this case, having to create one before fixing a critical blocker.
EoD? End of December? End of Death? (reference to world going to end)
That’s a lot of dollars, ching ching ching
got it; arse
It would certainly be an issue if you didn’t have one
The problem was named after an incident in 1996 in which AOL’s profanity filter prevented residents of the town of Scunthorpe, North Lincolnshire, England, from creating accounts with AOL, because the town’s name contains the substring “cunt”.
haha
those are terms, this is substrings within words
I haven’t seen branches or variables being called arse
Then again, I do like to catch exceptions as up
so I can throw up
Simple changes require only simple reviews.
Responsibility is shared. It’s not one or the other.
Many people don’t know what they’re doing. That’s kind of expected. But a tool provider and seller should know what they’re doing. Enabling people to behave in a negative way should be questioned. Maybe it’s a consequence of enablement, or maybe it’s bad design or marketing. Where criticism is certainly warranted.
Commit with Co-authored-by: Copilot
or maybe better --author=Copilot
It would certainly help evaluate submissions to have that context
oh, that’s a cool website
adds it to bookmarks and search bookmarks
But did it reach test or production environment yet? Or will it die in development environment.
Windows is / Windows filesystems are case insensitive too.