-
Notifications
You must be signed in to change notification settings - Fork 208
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is oboe.js dead? #238
Comments
I wouldn't like to think so but the evidence as you have put it would suggest otherwise. I don't have permissions to do releases etc. With other contributors having less time it became impractical. Would be great to pick it up again but I think some of the issues and advances in streaming and things like that mean a full new version that is built in a different way. We'd discussed having more specific implementations for node and the browser etc. |
I just discovered this cool tool. But it seems inactive for quite a while. Is there an alternative library or is there any roadmap / plan / issue list for us to set up a full new version if I'd love to contribute. |
I think it is a rather unique library in the JS space. I couldn't find anything like it. The current version is pretty robust and stable although I found a bug today. I'll report it and see if it gets any traction. |
Here are two forks of the SAX parser used in Oboe that look like somebody maintains them. https://github.com/dscape/clarinet and https://github.com/KeeeX/sax-js |
The last release is precisely three years ago and there have not been any code contributions in a year and a half.
Should the project be considered dead/unmaintained? Do you have any recommendation for alternatives?
Thanks!
The text was updated successfully, but these errors were encountered: