[1] https://www.reddit.com/r/mac/comments/1k07yqj/sharp_edges/
[1] https://www.reddit.com/r/mac/comments/1k07yqj/sharp_edges/
Deleted Comment
Maybe it’s just easier to throw ‘AI’ (heavy compute of data) at a search problem, rather than addressing the crux of the problem…people not being provided with the tools to query information. And maybe that’s the answer but it seems like an expensive solution.
That said, I’m not an expert and could be completely off base.
If you looked at $ spent/use case, I would think this is probably the bottom of the list, probably with the highest use of that being in the free tiers.
Looking at the actual stats, you're a bit of an outlier: https://aaafoundation.org/wp-content/uploads/2023/09/202309_... (p. 12). The average commute trip is 22 miles, and keep in mind you also could use a level 1 charger at home.
For most, the purpose of living further from work is reduced total cost of living, especially if you're near a big city [2], where it's not usually an option. I save thousands a month by commuting a little, for the same number of bedrooms (which has a legal minimum where I am). If I wanted the same square footage, I'm saving > $10k/month, compared to being 1/3 the distance from work.
[1] https://www.census.gov/topics/employment/commuting/guidance/...
[2] https://www.tandfonline.com/doi/full/10.1080/02723638.2022.2...
Then make it valid UTF-8. If you try to solve the long tail of issues in a commonly used function of the library its going to cause a lot of pain. This approach is better. If someone has a weird problem like file names with invalid characters, they can solve it themselves, even publish a package. Why complicate 100% of uses for solving 0.01% of issues?
I think you misunderstand. How do you do that for a file that exists on disk that's trying to be read? Rename it for them? They may not like that.