• 2 Posts
  • 72 Comments
Joined 4 years ago
cake
Cake day: June 2nd, 2020

help-circle

  • 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’ve never understood the argument. It seems to have kind of been collectively hallucinated into existence by waves of internet comment sections over the years. But these aren’t mutually exclusive, and nobody has made a case that the resources for these other features are compromising the ability to deliver core browser functionality.

    They also seem to assume that it’s development decisions, rather than Google leveraging its search dominance and financial muscle, that are tied to changes in market share. I actually think these value-adds can be good, can punch above their weight and can, if they are smart in picking their spots, do so without necessarily compromising their ability to advance the development of Firefox.

    And nobody ever stops, breathes in and out, collects the evidence and makes the actual case. It’s just kind of assumed, asserted, repeated, assumed again, repeated again ad nauseum. Because enough people have seen other people say it, so they say it too knowing it leads to upvotes.

    The ones closest to citing evidence, thankfully understanding at least how a real argument would actually work, are also the most unhinged, which probably isn’t a coincidence.



  • I see this as revisionist history. Mozilla has long been beloved for a whole host of FOSS reasons, that align with the same reasons FOSS enthusiasts like anything FOSS. I do think there are fanbases for things who think their object of adoration can do no wrong (e.g. Sneako fans probably). They are out there, but I don’t see that as being true of Mozilla.

    I’ve seen supporters of Mozilla make nuanced points about it being an imperfect but important diversification of options that prevents Google from dominating the browser space, often in thoughtful interactions with fans of (say) the Brave browser or Opera browser over the fact that they rely on Chromium which is sustained by Google.

    Those convos have more going on than uncritical adoration, and imo it’s important to let those nuances breath so that they, rather the oversimplifications, can be our primary takeaways.

    Interestingly, while talking in mournful past tense about Firefox’s having lost their way, in this same thread there are people a few comments above denying that criticism of Mozilla is prevalent here. You guys should scroll up (or down) and say hello to each other.







  • 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.


  • Mate, we are discussing on two different threads. Chill out. Maybe I didnt get your point so feel free to elaborate or leave it.

    I think it would be really good if all of us on the internet agreed to a rule, which is that if you mischaracterize someone or misread them, it’s not that weird for them to want you to not do that. So I don’t think it’s fair to response to a comment correctly noting they are being mischaractized by going out of your way to try and make it about their emotions/mental state.


  • In what way did I bend your logic?

    Well for starters, the person above was pretty explicitly NOT advocating for reliance on third party libs, and perhaps more importantly, they were not in any way suggesting reliance on closed source software. In essence, diametrically the opposite of everything you were talking about.

    I think your confusion came in their phrasing of not relying on “labor product.” I took them to mean, not relying on people committing their free labor to sustain FOSS. I think you must have read that as not supporting FOSS.

    Also - not constructive? But you’re the one that’s being negative.

    I think they are right. You took the exact opposite of what they said and “corrected” them for it, which is irritating as hell. And now you’re doubling down, which is worse. I would be irritated too!


  • abbenm@lemmy.mltoAsklemmy@lemmy.mlDo you use Discord or Matrix?
    link
    fedilink
    arrow-up
    1
    arrow-down
    1
    ·
    edit-2
    6 months ago

    Are you sure that you actually know how to browse the rooms? I just opened my app, and I see, just for some examples, Linux gaming, vegan, and pine 64 all having activity within the past hour or so.

    I mean it’s no discord by any stretch, But you’re actually straight up saying that even the most active ones are 100% dead, there’s something going on with how you’re browsing and looking at the rooms.

    I feel like one of the biggest communication problems with stuff relating to open protocols or fediverse stuff, is that no one knows the lay of the land, there’s no broadly held consensus of whether things are active or not, what the culture is like, and you end up with people making confident matter of fact statements that are just transparently not true based on cursory examination.

    When Mastodon was new, reporters would just make matter of fact claims that one of its downfalls was that instances couldn’t connect with each other, even though that was called federating and just one of the most basic built-in features. Not that I’m the biggest fan of Blue Sky, but now that people are talking about blue sky, I’ve seen people just matter of factly claim that Blue Sky was 90% furry porn and rage bait. A totally outrageous claim, not even remotely aligned with my experience, but, just because there’s no settled consensus about what’s going on, there’s not really any disincentive for someone just coming in and randomly saying that.


  • Because it’s pointless.

    This is like Marvel Movie brain except applied to OSs. This mindset suggests that the only conceivable rationale for an OS is that it’s tied to shiny brand names and commercial rationalizations.

    Despite this insistence, numerous alternative OS’s do in fact exist and have been listed here. And the range of motivations extends beyond just having glossy icons for whatever the first 3 or 4 companies that pop in your head.

    You have:

    • experimentation and novelty/niche interest that don’t align with specific commercial interests (e.g. Menuet OS, TempleOS)
    • user-oriented design philosophies with specific definitions of speed and useability (e.g. Haiku OS)
    • study/teaching in academic context
    • niche/emerging product categories (QNX)

    If you are able to understand why people would have these kinds of interests, it’s the kind of thing that lights a fire in your mind, and for some people, sets them on a career, or opens up a major new interest, or leads to them having fun with projects that scratch their own itch, so to speak in ways that do lead to commercial applications (lest we forget that every FAANG has an origin story about how it started with tinkering in a garage). “Because it’s pointless” makes me feel like I’m witnessing that inner fire of curiosity and sense of possibility die in real time.

    It doesn’t mean there’s no barrier to market penetration or no difficulty creating a kernel, but there’s so much more to the WHY of creating an OS than getting listed on Nasdaq.