@freakboy3742 @glyph @jacob @sgillies I'm hesitant to share specific examples like that, because we may build something totally different! Or decide that the specific idea isn't good! But part of what we want to do is experiment. So while I worry about people anchoring on any specific idea we share, I also sense and understand a desire for those specific ideas / examples :)
@freakboy3742 @glyph @jacob @sgillies But the core of what I want to do is this: build great tools, hopefully people like them, hopefully they grow, hopefully companies adopt them; then sell software to those companies that represents the natural next thing they need when building with Python. Hopefully we can build something better than the alternatives by playing well with our OSS, and hopefully we are the natural choice if they're already using our OSS.
@charliermarsh @freakboy3742 @jacob @sgillies I certainly hope you succeed. I think there are ways that this could go bad, but I don’t think it *needs* to go bad. There are some significant challenges on the way there which need to be addressed as they come, there’s nothing to do or say right now, today, that can fully address those concerns
@glyph @freakboy3742 @jacob @sgillies Thank you I appreciate this
@charliermarsh @freakboy3742 @jacob @sgillies in a way I feel bad being critical! You and the team are doing great work, I don’t begrudge you for taking money for it, and my concerns are more like “when the investors push Charlie out for poor EBITDA performance in a down market cycle, how is the new management going to be incentivized to maintain things in a way that serves the community’s interest”, which is obviously at least a few years away