My point was that it "is" a windows thing, sufficiently documented in plenty of other creation software such as databases, other languages, and in some of Ms's own languages, hence it is a 'duck'.
My second point was that (as many of those linked topics show) there are ways to work around it, using Lc or any other language isn't likely to stop you from having to work around it, and if this "significant potential clientbase" is going to use (or not) Lc due to it, they will I assume not be a client base for any other programming language that has this issue *solely* because of how MS designed their OS.
SparkOut wrote: ↑
Thu Sep 27, 2018 7:50 pm
...the impression that the response to problems relating to Windows is "not to use Windows because nobody likes it."
You are the only one I heard say that exactly that way. I used (and supported) windows based systems for years, I have no beef with Ms despite my not using their os today, anymore than I have a beef with chevy or ford if I drive a dodge.
Windows suited my flow for those years, 'nix suits it better now, and while I don't agree with a whole lot Ms does these days, it doesn't take away from my feeling that they contributed more to bringing about the desktop computer revolution (from the main frames we used to deal with) than almost anyone else.
That aside, I don't see it as someone else's job to fix a (perceived) shortcoming in their OS. If you feel like thats a knock, well, I'm certainly sorry you feel that way, but I'm not going to try to spray sunshine up your backside either.
**ALL of the above is an *opinion* solely credited to the author of it and is not intended to reflect on any other entity, corporate or consumer, or any non-human, bigger than a bread box or not.