On Thursday, 6 September 2018 at 12:33:21 UTC, Everlast wrote:
The problem is that all projects should be maintained. The
issue, besides the tooling which can only reduce the problem to
manageable levels, is that projects go stale over time.
This is obvious! You say though "But we can't maintain every
package, it is too much work"... and that is the problem, not
that it is too much work but there are too many packages. This
is the result of allowing everyone to build their own kitchen
sink instead of having some type of common base types.
I doubt having too many packages will be D's downfall. Javascript
is a thriving language even if tons of NPM packages are
unmaintained (and even if they still run, they potentially have
security vulnerabilities due to old dependencies).
It's sort of like most things now... say cell phone
batteries... everyone makes a different one to their liking and
so it is a big mess to find replacements after a few years.
See, suppose if there were only one package... and everyone
maintained it. Then as people leave other people will come in
in a continual basis and the package will always be maintained
as long as people are using it.
If we could have something as simple as "having the one and only
package that fits every use case", we wouldn't have multiple
OS's, multiple programming languages, etc.
I do agree that having "the one" would make everything easier in
theory, but reality isn't theory.
