> Even if some company were to make a closed source fork, who cares?
They can add sufficiently popular functionality to said closed source fork and make the open source original a) obsolete and b) incompatible with the combined ecosystem, and thus deprive the users of a feasible free option.
From the individual incentive standpoint, it's not immediately clear who would make a decision to establish such a pipeline and subject their organization to short-term competitive disadvantage. A CEO of a public company can't really say "our R&D is 2x our peers because we're building a pipeline".
What I suspect is going to happen is something like the regional pilot situation, where one toils for pennies at lower levels and then gets to comfortable compensation numbers 10-15 years later.
People don't, organizations do. I spent 25 years employed by large corporations, and for literally anything that claims to improve team morale, productivity, etc. there is always a sufficiently high-level person that once attended the training, reckoned it wasn't a total disaster, and hired the vendor to cater to their team to get a bullet point on the "team building" section of their performance review.
I order a (free, due to my Sip Club subscription) coffee every day, sometimes twice a day. What I really want from the Panera Bread's kiosk is being able to wave my phone next to it, take a cup, fill it, and be on my way -- without having to click through all that nonsense on a greasy screen. Like the author, by now I can probably go through the sequence with my eyes closed, but I do personally consider it one of the most obnoxious UX fails in my daily life.
To me, Python is a great language for anything that needs to be written quickly and executed a few times and/or on a small scale. I'm a C/low-level guy primarily but I write a lot of Python code (probably more than C these days) for various purposes, and none of it is related to statistics or machine learning.
I've just read a post on Reddit, in which a middle-aged man with family suddenly realized that his (appropriately aged) daughter watches videos made by middle schoolers and leaves comments like "you are a cute boy". Much to his horror, under his account.
In one of the systems I worked with each ticket had an "assignee" (who did most of the work), a "tech lead" (who knew what's going on and could provide status and guidance), and an "executive owner" (the person you'd escalate to if needed). I suspect those were custom fields and schema could be extended further if desired.
That's how you get individuals who insist that you attach their name to your ticket (or better yet, do it themselves) after they helpfully inform you about an automated test failure in your commit. "Relentlessly mentoring team members on culture of quality" et cetera.
They can add sufficiently popular functionality to said closed source fork and make the open source original a) obsolete and b) incompatible with the combined ecosystem, and thus deprive the users of a feasible free option.