pepijnve commented on PR #16397:
URL: https://github.com/apache/datafusion/pull/16397#issuecomment-2971445102

   Sorry to go a bit off topic for a sec, but there's some context I would like 
to add. I worked on API design of a commercial software library with tons of 
extension points for 10+ years where backwards compatibility of the public API 
was something we stuck to religiously because of the burden API breakage places 
on the entire user base. Doing that kind of work for an extended period of time 
makes you think three times about new API and all the hypothetical uses and 
abuses; perhaps a bit too much.
   
   Relevant question to this text and the project is what the project's stance 
is wrt API stability? Merging fast means you're likely to ship something a 
little bit too quickly every now and then. I'm not saying it's a bad strategy, 
just wondering how you balance the tension between stability and velocity.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: github-unsubscr...@datafusion.apache.org
For additional commands, e-mail: github-h...@datafusion.apache.org

Reply via email to