Key Points#
- How to do open source
- The uniqueness of open source communities lies in the participants' genuine desire to contribute.
- If your open source project is too perfect when released, no one will want to participate, so you should open source it at the early stage of the project.
- For example, Deno.
- Learn to say no to unsuitable features.
- Open source projects should have good documentation and comments to encourage active participation, as most people are lazy.
- Not welcoming, not worth involving.
- People come to your
README.mdjust to find what they need, not to admire your cleverness and fancy features.
- Personal growth of developers
- Developers must use open source tools.
- Open source projects are the best challenges for developers.
- Motivation for doing open source
- Max Howell: I'm aiming at making software that works, starting from the package manager.
- Challenges faced by open source projects
- Insufficient sponsorship to solve difficulties for open source projects like log4j.
- Max Howell's insights on programming languages
- Use TypeScript, JavaScript is not good; use Rust, abandon old-fashioned C++.
- C++ makes the type system seem awful, but it's not always the case.
- PHP succeeded by providing what people need.
- PHP shows that people do not always have good judgment.
- Use TypeScript, JavaScript is not good; use Rust, abandon old-fashioned C++.
- Promoting their new project tea.xyz
Afterword#
Last August, while doing course experiments in the laboratory, I watched a live broadcast and made a few observations.
Actually, if you want to do something well, just do it, especially in the field of programming.
But once you start, you never know where to start.
I'm afraid that once I learn a set of technology, it will become obsolete.
Or the product ideas I come up with already have competitors.
So at that time, I went to see the experiences and opinions of the experts, and was influenced by them.
But now, I think it's better to solidify the foundation first (laughs).