Passionate developer in Java and Scala. And sometimes, something else. A few months per year, someone calls me "professor". CoFounder of Scala By The Lagoon @scalagoon
It is well within the authors' rights. It's not on him to provide you with bug-free code, it's on you to check if the code you use with an open licence is up to what you need.
I am not saying it isn't. I am saying he deliberately broke it knowing it would break all the projects who relied on it and had nothing to do with the kerfuffle.
Passionate developer in Java and Scala. And sometimes, something else. A few months per year, someone calls me "professor". CoFounder of Scala By The Lagoon @scalagoon
They HAD something to do with it: they depended on it.
Was it an aggressive move, that caused problems? yes.
Was it within what the licence and copyright laws permit him to do? yes, too.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
It is well within the authors' rights. It's not on him to provide you with bug-free code, it's on you to check if the code you use with an open licence is up to what you need.
Uh...except he deliberately did it.
It's still within his right's. It's MIT, it's very forward about being warranty free.
I am not saying it isn't. I am saying he deliberately broke it knowing it would break all the projects who relied on it and had nothing to do with the kerfuffle.
They HAD something to do with it: they depended on it.
Was it an aggressive move, that caused problems? yes.
Was it within what the licence and copyright laws permit him to do? yes, too.