• 0 Posts
  • 17 Comments
Joined 1 year ago
cake
Cake day: June 9th, 2023

help-circle
  • That’s not really a common situation though. Sure, people might use the BSD license on something they did as a hobby, or just to learn things. But, the scenario described here is more like:

    A group of people all have the same little problem, and they work together to come up with a solution for it. They solve the main problem, but their solution has a few rough edges and there are similar problems they didn’t solve, but they’re not motivated to keep working on it because what they have is good enough for their current needs. So, they put out some flyers describing how to do what they did, and inviting anybody who’s interested to keep working on improving their fix.

    A company comes along, sees the info, and builds a tool that solves the problem but not quite as well, and for a small fee. They spend tons of money promoting their solution, drowning out the little pamphlet that the original guys did. They use as much IP protection as possible, patenting their designs, trademarking the look and feel, copyrighting the instructions, etc. Often they accidentally(?) issue legal threats or takedown notices to people who are merely hosting the original design or original pamphlets.

    Maybe the original inventor didn’t get screwed in this scenario, but you could say that the public did.



  • Code review, QA team, hours of being baked on an internal test network, incremental exponential roll out to the world, starting slow so that any problems can be immediately rolled back. If they didn’t have those basics, they have no business being a tech company, let alone a security company who puts out windows drivers.


  • No they won’t, not if they’re in the slightest bit competent.

    Blameless post-mortem culture is very common at big IT organizations. For a fuck-up this size, there are going to be dozens of problems identified, from bad QA processes, to bad code review processes, to bad documentation, to bad corner cases in tools.

    There will probably be some guy (or gal) who pushed the button, but unless what that person did was utterly reckless (like pushing an update while high or drunk, or pushing a change then turning off her phone and going dark, or whatever) the person who pushed the button will probably be a legend to their peers. Even if they made a big mistake, if they followed standard procedures while doing it, almost everyone will recognize they’re not at fault, they just got to be the unlucky person who pushed the button this time.







  • Linus is the one who got a workable thing out in the public’s hands. He didn’t even want to name it Linux, but someone came up with that name and it stuck.

    The GNU project did a lot of great things, but ultimately they weren’t able to get a full-fledged operating system out that people could use, so they lost the opportunity to name it. It really shouldn’t matter to them though. GNU is well known, its philosophies are critical to how the free software and open source communities work, it was basically a massive success in the way almost no other volunteer non-commercial projects ever are.

    But tagging “GNU/” in front of Linux is dumb.




  • Nah, Starbucks is MacOS.

    It’s more expensive than it needs to be, but it looks really pretty, and fundamentally it’s still coffee, just like MacOS is Unix-based under the hood.

    A chromebook is more like a can of coke. It’s caffeinated, has mass-market appeal, but nobody’s going to be spending hours talking about just how great their can of coke is vs. someone else’s can of coke. A high-end chromebook is maybe a glass bottle of Mexican Coke.