License
Any chance you could switch to a more permissive license like MIT?
Thanks for your hard work on this!
Could you elaborate as to why you feel that Apache is not permissive enough? E.g., what would MIT allow you to do that Apache does not?
(I am genuinely curious, I am not trolling.)
Include it in PostgreSQL, whose license is closest in similarity to the MIT license.
@geofflangdale will need to confirm, but I find not objection to adding the MIT license. I would keep Apache, however.
I don't have strong opinions about licensing in this regard; I was, IIRC, just copying the license from simdjson. I am marginally concerned not about licensing but about someone picking up this codebase which represents an aspirational and theoretical idea that "the ideas in simdjson should be applied to csv parsing" without any real thorough engagement on my part (or anyone's, as far as I can tell) to ensure that the system is sane and reasonable in terms of a) how people really use CSV in practice and b) how someone might want to use a CSV parsing library.
I don't currently have the resources to make either of these things happen - I've recently taking on a new fulltime job and have a pretty full-on side project. If someone wants to work on this I'm happy to make changes to the licensing to help them make this skeleton into something useful - although I would be just as happy if they wanted to loot whatever marginal intellectual contribution that simdcsv makes and start their own project. :-)
@geofflangdale
I would be just as happy if they wanted to loot whatever marginal intellectual contribution that simdcsv makes and start their own project
They have to feel like they have permission to do it.
If you allow me, I will just enable dual-licensing (MIT+Apache).