• Skip to primary navigation
  • Skip to main content
  • Skip to primary sidebar

Customer Servant Consultancy

Where we develop robust web sites with emphasis on accessibility

  • About
  • Our Work
  • Code Snippets
  • Testimonials
  • WordPress With A Screen Reader
  • Let’s Talk
  • Read
  • Note
  • Article
  • Bookmark
  • Like
  • Watch
  • Reply
  • Listen
  • Quote
  • Repost
  • RSVP
  • Issue
  • Video

FOSS was never about trust in software owners. It was about not needing to trust them to begin with

30 November 2018 by Amanda Rush Leave a Comment

Read De-facto closed source: the case for understandable software

Code is the only thing you can trust when you want to know what the software is doing, when the company goes belly up, or when your system isn’t the same system that the original authors were developing on.
Code is the only thing you can trust, and by not reading it, you’ve forfeited the most important benefit provided by this ecosystem: the choice of not having to trust the authors regarding behavior or continuity.

This is a good read regarding the event-stream ongoing saga, and I agree with it, but I also have some things to add to it. For those of you who may not be familiar, (non-developers), event-stream was pulled from Node Package Manager, (something that gets used pretty frequently when building software in order to manage dependencies, otherwise known as other code bits you need in order to run/build your code bit), because it relied on another package which was found to have vulnerabilities. It was then handed over to someone else, who promptly added a cryptocurrency iner to it, at which point the internets freaked out. Frankly I don’t completely blame the new maintainer for adding the cryptocurrency miner. There are very large corporations who have no problem using open source software for their benefit, all while not supporting the maintainers. See for example: Apple and Microsoft. And if you can’t be relied on to hit that donate button, well then we’ll just use your processing power because eating habbits need to be supported. I’d like to add to the post I’m linking to though that, while I think code does need to be simpler and thus easier to understand, I also think maybe we need to simplify our build processes. But back to the “understanding” point, reading code is a learned skill, and I think to a certain extent it’s on the users, (and in this case the users are developers), to learn how to read code. As much as I’d like code to be simpler, outside of everyone who writes code taking courses/reading books on best practice and then applying all that, I don’t see this happening.

Also on:
  • IndieWebCamp Icon indieweb
  • brid.gy

Filed Under: open source


Respond

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Primary Sidebar

Copyright © 2021