Running on prem or homegrown systems used to be considered a core competency of having a computer science department and a campus-wide IT/networking staff at a university. In the environment that exists today in academia, for instance, BSD would never be created because somebody could just pay a third party external vendor for some packaged product. What happened in the past 20 years to change that? I really wonder.
But you don't extend that same argument for an agricultural research department by asking them to have a homegrown farm for supplying the university with food!
I dont think a competent CS department requires their being a homegrown or on-prem system for use in the university. That could happen, but if resources could be better spent by purchasing rather than building, then that should be the correct choice.
Well, even in the mid 80s for example when many universities and their CS departments were heavily into DIY in house software development, none of them were expected to write all of the software used by all of the university. Ordinary workstation platforms were still purchasing MS-DOS 3.3 licenses with their hardware or Mac OS with their macs, etc. And things like Microsoft Office, Wordperfect.
Universities which do have large agriculture/farming related departments often operate their own small scale test/development/experimental farm.
