For Mojo, I'm interested in seeing how the language can be used as a path forward for the Cython community. This could be a stepping-stone towards reimplementation of Python in Mojo. For the past 3 year, I have been talking about the need for a Python-Steering-Council-recommended extension language for Python. This will be particularly important as WebAssembly keeps progressing and potentially redefining what we mean by virtualization and containers.

We have already been using LLVM extensively in Numba and there have been several explorations around MLIR and related technologies. There are several potential paths forward and I'm looking forward to finding ways to cooperate.

Understanding what will be open-source is of course, critical for that.

There is some work to bring it up to 3.12 and some resistance to merge it into 3.X because of the impact on extension modules (they all have to be recompiled and in some cases changed a bit).

If you are interested in it, reach out to Sam. He has done a pretty impressive piece of engineering work.

I am sincerely interested in seeing if the HackerRank leadership will reach out and discuss. I was not intending to promote anything I'm doing right now. I suspect they won't but I will talk to them respectfully if they do.

Let's promote the SymPy maintainers, though. Let's also promote NumFOCUS, because they do a valuable service to community-driven projects and could help SymPy respond to this sensibly. Let's also promote NumFOCUS because they efficiently and tirelessly work to help the projects they fiscally sponsor (like SymPy) -- providing legal support: https://numfocus.org/.

Perhaps something good can come out of this, still.

I appreciate the "fix-it-twice" attitude implied by the RCA promise (Root Cause Analysis for those who also had to look it up). Also, consider recognition and restitution for the unnecessary work you created for the NumFOCUS director, a NumFOCUS lawyer, and the SymPy maintainers.

A $25k donation to NumFOCUS would be a good start.

If you are willing to talk about what happened publicly, I'm starting a podcast/video series to discuss business and open-source. This would make an interesting conversation. Perhaps we can turn this into a positive to raise awareness and inspire better behavior in the industry? Ping me.

It currently emits Cython for the C-backend (and PyIodide). It is very alpha currently, but if people are interested in helping, get in touch.

Business owners and managers do need to understand that they may have to rewrite the software from the ground up because the first version will have all the problems the author talks about.

Most business owners and managers actually do understand this already. The goal of the first version is not to be architecturally perfect. The goal of the first version is to see if anyone will care if it exists. This is a good argument for not always building on the first version of a startup idea -- but actually build it again once you know people will buy.

Comments URL: https://news.ycombinator.com/item?id=27762693

Points: 3

# Comments: 0

Comments URL: https://news.ycombinator.com/item?id=25050558

Points: 5

# Comments: 0

He introduced me to the ideas in this paper that he induced from his own observations of his “mystical” experiences.

It is fascinating to realize these self models exist in a wide variety of animals and the modeling of others is what makes some animals different.

In “Sapiens” https://books.google.com/books/about/Sapiens.html

Yuval Harari argues that Homo sapiens took over all other Homo species because of the development of “myth” which may be related to the Hyperactive attribution of consciousness referenced in the article. Humans cooperate at scale much better than any other species (but also fight at scale more aggressively) because we can communicate about abstractions.

Very interesting inter-related ideas.

The real challenge comes, however, as you try to build an ecosystem of libraries on top of multiple different APIs. You end up reinventing the wheel or struggling to maintain multiple versions of the same library.

Some cooperation is immensely helpful at the lowest level, and we hope ultimately to be helpful to the different tool builders in providing information and guidance about what is already a standard and agreed upon in the space.

This is not about establishing or forcing behavior. It is about documenting and clarifying best practices that have already emerged as well as potentially giving libraries a way to signal to downstream developers of additional libraries that they adhere to the standard.

My own thoughts go in the direction of maybe the right thing to do is different at different "scales". The right thing to do in my family is different than the right thing to do in my job which is probably different than the right thing to do at the city level, the county level, the state level, the nation level, and the world level (to use labels appropriate for the USA). Leaders at each level have a different decision to make and things work better the more people we have making "good" decisions at each level. The process of figuring out what "good" decisions at each level is the really hard part that is not easily wrapped up with platitudes, memes, or other projections into a single one-dimensional axis (i.e. left vs. right) of a high-dimensional, multi-attribute space.

I have had the privilege of watching open-source projects I started or participated in get used by millions. I want to see a world where more people are paid a great living to work on open-source software. There are several approaches to improving the funding fabric for open-source. OpenTeams is one of them. Quansight Initiate (http://www.qi.ventures) is another one. Quansight Labs (http://labs.quansight.org) and Quansight (http://www.quansight.com) are others. A group of us are also working on a few other ideas including FairOSS (not going to give the website because it is a behind-the scenes operation for now --- ping me if you are interested in learning more).

I have spent many years writing open-source software, improving open-source ecosystems, hiring open-source developers, and paying people to work on open-source software. I have also spent the past 12 years in particular working in industry watching open-source get used and seeing the disconnect between open-source usage and open-source communities.

There are several business models that can work to improve things. With OpenTeams we are building out a platform and ecosystem to help open-source communities thrive by directing money from industries that use them to the communities that exist while also learning from the basic laws of incentive alignment and local choice making that are at the heart of every economy.

One of my core believes is that not all software will be or should be open source. I don't make this conclusion lightly. However all software will be based on and use open source foundations. Those communities that produce these foundations should be able to thrive and yet retain their freedom and self direction.

OpenTeams is a platform to make that happen by connecting companies that use open-source and want to fund specific features and improvements with organizations that hire open-source developers to work on proposals that have input from community participants and leaders. Some initiatives will be new projects, some will be usability improvements and feature proposals for existing projects. An effect of OpenTeams is also to enable a place for all open-source contributors to build their reputation (not just contributions that lead to pull-requests).

We are in a pre-alpha stage at the moment, but will be continuing to add features and are open to suggestions and ideas.

Thanks for your feedback.