I argue it's not Open Source (Freedom, not Free Beer) because PRs are locked and only Hipp and close contributors can merge code.
It's openly developed, but not by the community.
You can certainly argue that, but that's not what Open Source or Free Software has ever been. It's about your freedoms as a user, you are always free to fork with a different model. I think the expectation of "open contributions" is quite damaging, to the point where peple/organizations are hesitant to release their software as open source at all.
That's not what Open Source means. The development team not being willing to review your pull requests does not limit your freedom to use sqlite in any way.
> In order to keep SQLite completely free and unencumbered by copyright, the project does not accept patches. If you would like to suggest a change and you include a patch as a proof-of-concept, that would be great. However, please do not be offended if we rewrite your patch from scratch.
SQLite is open-source, meaning that you can make as many copies of it as you want and do whatever you want with those copies, without limitation. But SQLite is not open-contribution. In order to keep SQLite in the public domain and ensure that the code does not become contaminated with proprietary or licensed content, the project does not accept patches from people who have not submitted an affidavit dedicating their contribution into the public domain.
All of the code in SQLite is original, having been written specifically for use by SQLite. No code has been copied from unknown sources on the internet.
The insanity of requiring an open source project to be
hosted on a proprietary for profit Microsoft social
platform with git hosting makes my head hurt.
I thought this was how Shazam worked as well. I hummed a tune and was super disappointed it didn't identify it. Sounds like a business opportunity to me :)
I strongly doubt that. Adding a check to a simple increment instruction is likely slowing it down by more than 2x not 2% so it must be some whole program performance benchmark that's slowed by 2%.
The PEP says that a naïve implementation would cause a 4% performance hit and have a list of various ways of speeding up cases where immortality makes sense / is guaranteed that they say can bring this to parity. Maybe they implemented part of the list.
Yes, that is true. ChatGPT refuses to work with VPN and regularly checks for your IP using Cloudflare. Most of these new AI-driven startups are using Cloudflare. It is funny that startups collect/scrap data from all over the web but don't want to scrap their chatbot response without paid API. I guess it is life...