Re:License to Use JSLint for Evil
by the_pwner224 on Thursday April 14, 2022 @06:10PM
(#31033953)
It makes it impossible for most organizations to use, not for most people to use.
[ Parent
| on HN ]
Re:License to Use JSLint for Evil
by JoshTriplett on Thursday April 14, 2022 @06:33PM
(#31034242)
It also makes it impossible for Open Source projects to use and depend on. This isn't a companies-vs-people thing; people and projects who care about their users should not go "meh, whatever" about software licensing.
Re:License to Use JSLint for Evil
by pessimizer on Thursday April 14, 2022 @06:52PM
(#31034430)
Does Crockford care about Open Source?
People who aren't doing evil can use it. It's not compatible with FOSS. It's a linter, it doesn't require being incorporated into people's projects.
Making it proprietary would be more limiting, making it Free would also be limiting (in a good way imo.) He chose to make it his way.
Re:License to Use JSLint for Evil
by JoshTriplett on Friday April 15, 2022 @01:44AM
(#31036922)
And many people chose not to use it as a result, despite having no desire to do "evil". People can certainly license software however they like, and other people can complain about that and build replacements, as JSHint did.
> It's a linter, it doesn't require being incorporated into people's projects.
Many things do want to depend on tools that process source code, such as bundlers, IDEs, transpilers, and similar.