Great until someone realises you’ve filtered out minority groups from the application process (most developers are men so maybe the LLM decided they’re the best fit, but you’ll never know exactly why it screwed your over) and you suddenly have an expensive lawsuit
I guess watch out for different line endings in files "\r\n" in Windows, "\n" in Linux. The best thing to do there if possible is use tools in Windows that preserve Linux line endings so you never see "\r\n" in Linux at runtime.
If you're using classes under the System.Drawing namespace then a lot of functionality is missing in Linux, but I don't know much about that. The 3rd party ImageSharp library fills some of the gap and is just generally awesome.
Other than that, I'm sure there's niche things but nothing is coming to mind!
To get runtime case-sensitivity problems with filenames I guess you must be doing something like having resource files as part of your project and then loading them from disk at runtime, but the code that loads them is being told the slightly wrong filename. Depending on why you need to load those files, there's not much you can do about that except stop coding the wrong filenames!
There are things that can help with filesystem differences though, if you're not using them already look under the System.IO namespace
Path.Combine will combine path segments using the native directory separator either `/` or `\`.
Path.GetTempFileName will create a temporary file on disk so you don't need to know if that's `/tmp` or `C:\whereverwindowsputsit\`
Mostly everything just works when coding on Windows and deploying to Linux, I think it is only the filesystem differences that ever cause problems and even then it's down to coding mistakes.
protip: You can make synctrain sync with an iOS shortcut, with the shortcut being triggered when Obsidian is opened or closed. This means you're always in sync, even if iOS hasn't allowed synctrain to run in the background.
I like the idea of using the new app, but in the browser I can use ublock to remove the weird "Inbox Zero!" celebration. Is there any plan to allow that kind of empty inbox configuration in the app?
If revenue doesn't catch up with the cost of developing and running these huge LLMs then the only way to avoid an AI winter is to find a way to make them way cheaper to develop.
That's what he said, you aren't applying this change to your paying customers because you know what a shitty decision it is and only free users will put up with it.