Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lottery factor #5

Open
romainmenke opened this issue Jul 23, 2023 · 1 comment
Open

Lottery factor #5

romainmenke opened this issue Jul 23, 2023 · 1 comment

Comments

@romainmenke
Copy link
Member

romainmenke commented Jul 23, 2023

https://en.wikipedia.org/wiki/Bus_factor

This is related to financial backing / funding


  • PostCSS is 1 person
  • LightningCSS is 1 person
  • csstools tokenizer and parsing tools is 1 person
  • PostCSS Preset Env is 2 persons
  • StyleLint is multiple persons 🎉
  • CSSTree is 1 person
  • PostCSS Import is 1 person
  • esbuild is 1 person
  • ...

Too many important parts of the CSS tooling ecosystem are owned by only a single person.
This isn't ideal.

It is very rare for a single person to produce high quality software over very long stretches of time.

It is much more common that the software will be sub-par in at least some area's and that eventually their interest will drop and they move on.

A multi-person team, each with different backgrounds tends to produce better results over longer stretches of time.

@romainmenke romainmenke changed the title Lotto factor Lottery factor Jul 23, 2023
@belowi
Copy link

belowi commented Oct 28, 2023

https://en.wikipedia.org/wiki/Bus_factor

This is related to financial backing / funding

  • PostCSS is 1 person
  • LightningCSS is 1 person
  • csstools tokenizer and parsing tools is 1 person
  • PostCSS Preset Env is 2 persons
  • StyleLint is multiple persons 🎉
  • CSSTree is 1 person
  • PostCSS Import is 1 person
  • esbuild is 1 person
  • ...

Too many important parts of the CSS tooling ecosystem are owned by only a single person. This isn't ideal.

It is very rare for a single person to produce high quality software over very long stretches of time.

It is much more common that the software will be sub-par in at least some area's and that eventually their interest will drop and they move on.

A multi-person team, each with different backgrounds tends to produce better results over longer stretches of time.

While there are successful examples of software projects maintained by individuals, having a multi-person team offers advantages in terms of sustainability, quality, and the ability to adapt and respond to evolving needs. Collaboration and shared responsibility can help mitigate the risks associated with relying solely on a single person for critical components of the CSS tooling ecosystem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants