> A lot of the decrease is also correlated with access to birth control which drastically reduced accidental pregnancies which were a decent amount of the fertility rate
Its interesting, especially the size for edge applications. That being said, for something thats been worked on for two weeks by one person, you are going to have to bring a LOT of data and architectural explanation to convince folks this is better than DuckDB in any way. For example, where are the TPC and LDBC benchmarks?
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.
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.
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.
This was my first intuition.