@carkh i pulled, rebuilt, and ran testparsing.exe -- all results returned [OK] also, if you do decide to build clj-kondo and you haven't looked already, you might find the following useful: https://github.com/borkdude/clj-kondo/blob/master/doc/build.md#user-content-windows -- preparation of the appropriate build environment is annoyingly manual (uninstalling certain vs c++ redistributables + registry editing to get windows sdk 7.1 to install appropriately).
i also have a summary at: https://gist.github.com/sogaiu/e079cd770051685c46ab24b6658effcf
thank you @sogaiu , I'll keep your gist at hand
Thanks also for your testing ! As for the clj-kondo link, borkdude already provided it to me =)
ah, yes, failed to see it above 🙂
i haven't heard this mentioned yet, but iiuc, powershell core seems to run on "the 3" platforms in some capacity, so at some point it seems possible it may be chosen for portability and maintenance in some projects over bash.
not until all platforms install it from the start i think
i think it depends -- for developer-oriented projects where installation of pieces is a given, installation of powershell core is just another install -- i've been considering it for a few things so i don't have to muck around with bash on 2 platforms and something else on windows.
I come from the other direction, projects ought to make it as easy as possible to be used, though without sacrificing core values
if it makes life easier it's acceptable depending on the uptake of core i guess
there is the deployment portion, which i agree should be made easy to be used -- for the clj-on-windows case, yes, installing powershell core is likely to be somewhat of a burden for macos and linux distributions atm, so it's not currently a great story. for other projects where the powershell core requirement is only for building (and not running) the end product, it seems less problematic to me. it would be nice if the actual building process were easy too, but there often appears to be a trade-off involved where making something easy-to-build on multiple platforms is sometimes (often?) at the cost of making it harder to maintain.
multi-platform is a nightmare in itself, there is a reason java is so big, and still it doesn't manage to fully abstract the underlying os
diversity is good though
if not for maintainers =)
i agree, single platform is not healthy
same for browsers 🙂