• 1 Post
  • 22 Comments
Joined 4 years ago
cake
Cake day: June 2nd, 2020

help-circle





  • It’s probably a coincidence that shortly after Mozilla acquires an ad company, they “accidentally” remove an ad blocker.

    I mean I’m of two minds here. One, there’s an epidemic of intellectually lazy, kneejerk Mozilla hate and it’s time to turn the tide on that.

    But on the other hand, even as a Mozilla fanboy I can see how this is a really bad look, and really indefensible. I think it’s more of a huge error of judgment, and if there are other huge errors, I can begin to see a problem, but I think they have too much of a positive track record in their history to just go reaching for the tinfoil hats so quickly.






  • The best I can think of is that the explainer language used to justify the extension’s removal was just boilerplate language that got copy+pasted here because someone clicked the wrong button. But even that makes a mockery of the review process.

    I think “oops clicked wrong button” would be slightly more defensible, but not by much. If they truly rejected the extension for content in it that it does not have, it’s hard to see how a human could make that mistake even accidentally. But maybe there’s something I’m missing.



  • I had an alienware Steam Machine and it was perfectly fine.

    I think the criticisms of the Steam Machine suffered from what I would call the Verge Syndrome, which is only being able to comprehend things in a binary of instant success or failure, with no in between and no comprehension of other definitions of success.

    Steam Machines were a low risk initiative that were fine for what the were. They did not have a ring of death, they didn’t have a blue screen, the OS itself was not glitchy, they didn’t lose money, and they didn’t fail any stated goals. They got the Proton ecosystem up and running, and got the ball rolling on hardware partnerships, which led to the smash success of the Steam Deck which would not have been otherwise possible.


  • I agree that the steam machine was too early.

    I don’t know how it could ever start from zero without having to go through a growing stage. I think it was just necessary to have modest expectations, and so far as I can tell, valve partnered with third party vendors and didn’t lose $$$ on it.

    Moreover, the downstream effect has been to set the foundation for the Steam Deck, which has been a smashing success. It just takes time to build up a mature ecosystem.



  • Sorry, I was super unclear there. This was not Google.

    However, Google also sometimes has done their own April Fools bits, and historically Google has been big part of April Fools hijinks. So I did mention them as a company that does these, and I did post this which is impersonating Google as an april fools prank, but yeah, this particular one was not at all carried out by Google.


  • I almost forgot today was April Fools day. I feel like since Covid, the national mood ™ was such that Google and co stopped doing April Fools pranks, and/or if they did them, they were so safe they were groan inducing.

    Looking around at the roundup links for 2024, there aren’t many that happened this year, from the looks of it. So I wanted to post this one, because it’s the rarest of rare - one that I thought was really incredibly well done.




  • And again, that’s not even within an country mile of being a good faith attempt at charitable interpretation, for several reasons.

    You’re twisting their words into some sort seemingly overnight goodbye to all software relying on third party libs. A more normal way of taking that is envisioning a more gradual progression to some future state of affairs, where to the greatest extent possible we’ve worked to create an ecosystem that meets our needs. An ecosystem that’s build on a secure foundation of known and overseen libraries that conform to the greatest extent possible to the FOSS vision. Ideally you don’t just say goodbye, you work to create ersatz replacements, which there’s a rich tradition of in the FOSS world.

    Your other point was even worse:

    important software shouldn’t reuse code already made, they should reinvent the wheel and in the process introduce unique vulnerabilities

    Somehow, you decided that putting words in their mouth about going out of their way to solve the problem only with worst-case-scenario bad software development practices (e.g. lets go ahead and create unique vulnerabilities and never re-use code) is a reasonable way of reading them, which is completely nuts. FOSS can and does re-use code, and should continue to do so to the extent possible. And like all other software, strive to avoid vulnerabilities with their usual procedures. That’s not really an argument against anything specific to their suggestion so much as its an argument against developing any kind of software at any point in time - new games, new operating systems, re-implementations seeking efficiency and security, etc. These all face the same tradeoffs with efficient code usage and security. Nothing more or less than that is being talked about here.


  • we shouldn’t rely on free software made by free labor, and we need to say goodbye to some 60-70% or more of the software we use

    Again I’m just reading along, and as a person who cares about, you know, the principle of charity, I don’t see how you can possibly think that’s the most charitable interpretation of what they said. I took them to mean we should do what we can to ensure these projects have financial resources to continue, not that we should “say goodbye” to them.

    And here’s the crazy thing: I’m not even saying I agree. I just think it’s possible to address a face value version of what they’re talking about without taking unnecessary cheap shots.