2 ms·
I want to believe it's a good thing, but having to support a platform that doesn't support good ole symlinks is incredibly aggravating. Npm too would be much ea
by rektide 6y ago
I want to believe it's a good thing, but having to support a platform that doesn't support good ole symlinks is incredibly aggravating. Npm too would be much easier to work with if it could have had symlinks. If only there weren't some weird platform-I-don't-want-anyways's limitations gumming thing up. Microsoft extending their Microsoftisms into every software platform is a frustrating limitation to keep facing.
I'm fine with the general attitude of harmony and oh yay, a bigger tent for everyone, it doesn't bother me, and platform flexibility has it's upsides. But there really is a downside to this all too, and it goes unremarked. I want to at least put down some words, somewhere, to remark that Windows support is constraining & limiting. OpenJDK of course is cross platform & already supports Windows, but the sign that this is a proper & well supported thing in Windows will quite likely amplify Windows user's expectations that all the libraries & tools they run across are going to be catered to them & their experience. It increases a library maintainer's burden, supporting this new class of usually-not-that-expert users. I encourage us to reflect on this as a mini Eternal September event, of Microsoft extending the reach of their community into something that used to be a little more deliberate; that's maybe putting it a little strongly, but I think we can recognize the parallel.
To summarize, are more prevalent technical constraints, and re-emphasized demands upon open-source Java authors, in this shift to further allow & encourage Windows based Java development.