This assumes behavior on both sides of the implementation and has nothing to do with open source.
> Sure all the big companies that relied on dhcpcd will rewrite it.
Unlikely. dhclient works just fine and carrying a fork of dhcpd will work just fine.
You’re missing my point. When you work on open source and end up with millions to billions of users, everything you do ends up having a huge monetary impact (guess how much Roy’s bugs have cost the economy in lost time). However, that’s just a side effect of software, not you being some unsung hero.
Tons of people need software that does X. Once one or two people have an open source solution to X, people can just use that and move on. That’s a good thing but it doesn’t mean that those one or two people are critical to anything. If they quit, fail, whatever, downstream dependencies will just swap and move on.
> Sure all the big companies that relied on dhcpcd will rewrite it.
Unlikely. dhclient works just fine and carrying a fork of dhcpd will work just fine.
You’re missing my point. When you work on open source and end up with millions to billions of users, everything you do ends up having a huge monetary impact (guess how much Roy’s bugs have cost the economy in lost time). However, that’s just a side effect of software, not you being some unsung hero.
Tons of people need software that does X. Once one or two people have an open source solution to X, people can just use that and move on. That’s a good thing but it doesn’t mean that those one or two people are critical to anything. If they quit, fail, whatever, downstream dependencies will just swap and move on.