> No validation of inputs or helpful error messages - study the examples, read the docs.
I agree that validation is probably redundant, but why would you promote not having helpful error messages? Seems a bit elitist...
i might make a devmode version that has some of this in the far future. but it's not a priority before API stabilization, perf optimization, code golfing, tests, docs, examples and v1.
if anyone wants to contribute this, i would certainly entertain a PR, but no one is paying me to write extra code (or any code, really).
Fair enough, I understand the mentality, it's not easy developing and maintaining packages in your spare time...
But it's important to remember that thousands of hours of frustrated google searches:
'error: something not found'
And don't forget about support requests posted to the "issues" in the repo itself.
Ultimately spending an hour writing helpful errors can save you hundred of hours in support.
Of course you can just ignore everybody asking for help, but then if people aren't going to be able to use your project why make it open-source in the first place?
I love it! Having fun with your project is key :)
Keras is great about error message[1] and it's part of what makes Keras beloved (and heavily contributed to).
[1] https://blog.keras.io/user-experience-design-for-apis.html
i write open source code primarily for myself. doing anything i dont consider critical takes the joy out of doing it.
if people want features, they can fork and contribute code and then maintain that code, too...forever. of course, once you shift that burden to them, suddenly no one wants to get involved.
sorry for putting it this bluntly but it's the truth. i am one human, with a 9-5 and a life outside of coding. people seem to feel entitled to opinions on free open-source projects having contributed little-to-nothing.
i typically add them (or update the docs) once users encounter problems and open Github issues (reactively). doing it proactively is a waste of time (for me).
i accept the criticism. i just don't have the necessary free cycles to address it.
I would read them if they were linked from the readme :)
the purpose of posting it here is to hopefully get some alpha testing and feedback for more use-cases so it can be polished outside of my isolated purposes.
On the feedback side, a reset zoom button on the demos would be handy.
it's behind a double-click ;)