All the "infrastructure" code should be open source. It is better for everyone. I can't imagine a world where such code that enables others to write code (that may not be infrastructure) is not FOSS.
Paid services made available using that infrastructure code is also loosely called software (because programming is involved). But it involves other things as much as programming and hence making a business out of it makes sense if one has energy, passion and talent for it.
As a programmer, if you are in a position to do both, a balance is achieved.
If you are producing software that does not involve other things that a service has to offer, then it is better to just open source it right from the beginning or once you realize the force of open source.
And "free" in FOSS has an interesting connotation that Jamie Zawinkie said to have captured -- "Linux is only free if your time has no value".
Paid services made available using that infrastructure code is also loosely called software (because programming is involved). But it involves other things as much as programming and hence making a business out of it makes sense if one has energy, passion and talent for it.
As a programmer, if you are in a position to do both, a balance is achieved.
If you are producing software that does not involve other things that a service has to offer, then it is better to just open source it right from the beginning or once you realize the force of open source.
And "free" in FOSS has an interesting connotation that Jamie Zawinkie said to have captured -- "Linux is only free if your time has no value".