Voostind on open source libraries
In most areas in computer science, Open Source products follow after the commercial ones. Admittedly, first some pioneer thinks of a new technology and often releases it as Open Source, but the released stuff is never quite fit for production use. That makes sense, because it was a prototype; it was being pioneered. If it looks promising, commercial companies take it over, throw lots of money and expertise at it, and end up with a product that does make it into the market. Once a large group of people wants the same thing that commercial software already provides, but they don’t want to pay for it, then they try to mimic it.
Vincent also makes some interesting points about the relative difficulty of library and framework design compared to writing interpreters and compilers. Today’s must-read.
More recent articles
- ChatGPT should include inline tips - 30th May 2023
- Lawyer cites fake cases invented by ChatGPT, judge is not amused - 27th May 2023
- llm, ttok and strip-tags - CLI tools for working with ChatGPT and other LLMs - 18th May 2023
- Delimiters won't save you from prompt injection - 11th May 2023
- Weeknotes: sqlite-utils 3.31, download-esm, Python in a sandbox - 10th May 2023
- Leaked Google document: "We Have No Moat, And Neither Does OpenAI" - 4th May 2023
- Midjourney 5.1 - 4th May 2023
- Prompt injection explained, with video, slides, and a transcript - 2nd May 2023
- download-esm: a tool for downloading ECMAScript modules - 2nd May 2023
- Let's be bear or bunny - 1st May 2023