3 ms·
The video says that it's accurate that every night proprietary software is stealing citizen's healthcare data and that the solution is for the government to loc
by charcircuit 4y ago
The video says that it's accurate that every night proprietary software is stealing citizen's healthcare data and that the solution is for the government to locate all of the software it needs from scratch and open source it. Why stop at rebuilding all software from scratch? You will also want to rebuild computers from scratch, light bulbs from scratch, etc. The government doesn't need to invent everything from scratch. It can be cheaper and more effective them to buy goods and services from public companies.
The website has another message that publically funded software should be open source, but that's not always possible. The government may not have the rights to even do so if they outsourced some of the development. The software is often niche and would not benefit others. In fact it can be a security risk because attackers can look for security vulnerabilities or weaknesses in systems. Attackers have a much bigger insensitive to look for security problems than security researchers because there won't be a bug bounty, it isn't software they personally use, and it could be some rare piece of software no one knows or cares about. If most talented developers are working at private companies, that means that the remaining developers who chose to work for the government are likely more prone to have poor security practices. If attackers know the supply chain of the software they can attack it. If these are open source in the sense they take contributions attackers can contribute vulnerabilities. Open sourcing code is also extra work that has to be done and will make the software more expensive to make and maintain.
>Tax savings
>Similar applications don't have to be programmed from scratch every time
Buying existing software means you don't have to program it from scratch. Sharing projects with other agencies doesn't require open source.
>Collaboration
>Major projects can share expertise and costs.
This doesn't require open source either. The government if they didn't have an income stream from leaching off it's population would be incentivized to figure this out.
>Serving the public
>Applications paid by the public should be available for everyone.
Most of the software will be useless to the public.
>Fostering innovation
>With transparent processes, others don't have to reinvent the wheel.
This is just the collaboration point. The government isn't innovative in the software field.
- richbell 4y ago> If most talented developers are working private companies, that means that the remaining developers who chose to work for the government are likely more prone to have poor security practices. This is a fallacious logic. > Open sourcing code is also extra work that has to be done and will make the software more expensive to make and maintain. Not if there is an established standard and practice of writing code in an open source way.
- q845712 4y ago> > Open sourcing code is also extra work that has to be done and will make the software more expensive to make and maintain. > Not if there is an established standard and practice of writing code in an open source way. I've worked on closed source corporate software most of my career and then primarily corporate-sponsored open source in the last two years. In my own limited experience, it is strictly less work to have closed-source software. There's less concern / hesitations / hand-wringing over mover quickly when you have the illusion of privacy, and relatedly having a requirement that (almost) everything (eventually) becomes public only adds steps. Certain things always have to happen privately (examples include: internal discussions that include organizationally privileged information, certain CVE handling steps, fully secured builds with proper corporate attestations, and internal project-tracking) so you wind up with a private set of systems to maintain as well as the public ones. Maybe there's some orgs out there that "do it right" in terms of having OSS projects not add overhead, but I doubt it's possible in orgs with as much need for privacy and security as most fortune 1k co.s and governments.
- EMIRELADERO 4y ago> Maybe there's some orgs out there that "do it right" in terms of having OSS projects not add overhead, but I doubt it's possible in orgs with as much need for privacy and security as most fortune 1k co.s and governments. To the contrary, governmemt is where the need for transparency should be at its highest. Putting "efficiency" or "speed" above transparency about the inner workings of publicly-funded and publicly-made (by government employees) software is insane. There should not be any expectation of privacy for government employees in the field of records and information.