From a long-term #strategy #perspective, it is important to "dare" outlining not only the success of such projects, but also the consequences (for #society, project/tools/#platforns #ownership, etc.) and the most likely next steps that follow such succees.
The answers to those questions will most likely confirm the importance of using #openSource and NOT #proprietary solutions for any strategically significant elements.
@douginamug @falgn0n @tobykurien
Yes, and that may be(come?) important in each case where the proprietary software adequately does just that. IMO it is important to get more good examples from that camp.
Mostly, though, proprietary software has no intention in "walking those last miles" in this direction.
@FuzboleroXV @falgn0n @tobykurien This is a tricky one. The people I'm working with actually develop FLOSS, but there are several things for which there has been a choice to use proprietary.
But I think it is a false dichotomy between FLOSS and proprietary.
For example, does the proprietary software use open standards and allow you to easily switch services? Does proprietary software warp your sense of reality or turn you into a product?
I just want to point out that there are nuances.