3 ms·
It was a lot of work :). I knew making it usable by others would be as much work as writing it in the first place. It's definitely not fire and forget. I've be
by jmathai 16y ago
It was a lot of work :). I knew making it usable by others would be as much work as writing it in the first place.
It's definitely not fire and forget. I've been using it for over 4 years so I don't have any plans on ditching it. The main point of documenting it was so others would use it and I can improve on the library.
If you look at another one of my libraries on github (https://github.com/jmathai/twitter-async/issues https://github.com/jmathai/twitter-async/issues) you'll see that there have been over 90 issues raised by others which I've resolved. It's what's made that library so solid - hoping for the same here.
- jacquesm 16y agoIf I can find the time (fairly big if) I promise you that I will go through your code to see if I can either see things that you might improve or spot lurking bugs. Funny, you're jmathai, I'm jmattheij !
- jmathai 16y agoMuch appreciated. As far as a roadmap it'll probably continue to be what it's been. The next thing on the list are unit tests but otherwise it's whatever I or others using it feel the framework is missing (but wouldn't add bloat).
- checker 16y agoI'll admit I thought you were both the same person until this comment. Thanks for pointing it out.