This looks very exciting. I have a NodeJS binding I've been contemplating using SWIG. This appears to be much more straight forward. Looking forward to trying it out.
I've added a prebuilt image, so it should be straightforward to try it out. If you have any problems with working on that prebuilt image please open an issue or reach out to me!
Robust and mature SIP stacks which are still maintained are a rarity these days. I was pleasantly surprised recently to learn just how well this very mature library is being maintained. It seems like a great deal of effort has been invested to keep both the code and feature set relevant and up to date. Kudos to the maintainer.
Most other open source SIP stacks available either don't have the feature depth and breadth required for a serious SIP project: are only usable from a specific programming language, have been long abandoned, or have impermissive licenses.
> Most other open source SIP stacks available [...] are only usable from a specific programming language
Is that not the case for this library? It's written in C++, and didn't find any mention whatsoever about usage from other languages being an expected use case in the README. C++ can be used via FFI from other languages, but it's my understanding that it is difficult and error prone, unlike C which seems the perfect fit for multi-language libraries.
You have to consider the tail latencies of the system responding plus the network in between. The p99 is typically much higher than the average. Also, may have to account for GC as was mentioned in the article. 500ms gets used up pretty fast.
We are using Lit and MobX for a very complex real time communication and collaboration application. It is very simple and we have not had any issues with performance or flexibility.
I see a lot of folks complain about not getting help on OSS projects; I also see a lot of people turning a blind eye to people trying to help (however naively it may be). It's an intesting dichotomy.
> people trying to help (however naively it may be)
As soon as you are giving free attention and mentoring to people unable to make a somewhat useful contribution, you are giving up even more of your life for free.
There are people who know how to pick appropriate issues and send PRs with test cases. It might be better to look for them than try to mentor ineffective contributors.
Yup, it's interesting. I think a major cause is just a lack of perspective. Maintainers are likely working for free, have their own jobs and the like. They will appreciate it if you make their jobs easier, and will be extremely cautious if you are changing fundamental/core components as a new guy in town.
One needs to study on their own, use forums or get in touch in some other way that isn't a PR if they want help. Also, while studying the codebase, finding low hanging fruit is going to be easy. That's where everyone should start.
