• 0 Posts
  • 532 Comments
Joined 2 years ago
cake
Cake day: July 15th, 2023

help-circle

  • I think Ubisoft is clearly in the wrong, but you’re not making a good case. You’re conflating very different meanings of the word “own”.

    In terms of legal ownership, only the copyright holder owns the intellectual property, including the right to distribute and license it. When a consumer “buys” a piece of media, they’re really just buying a perpetual license for their personal use of it. With physical media, the license is typically tied to whatever physical object (disc, book, ROM, etc.) is used to deliver the content, and you can transfer your license by transferring the physical media, but the license is still the important part that separates legal use from piracy.

    When you pirate something, you own the means to access it without the legal right to do so. So, in the case at hand, players still “own” the game in the same sense they would if they had pirated it. Ubisoft hasn’t revoked anyone’s physical access to the bits that comprise the game; what they’ve done is made that kind of access useless because the game relies on a service that Ubisoft used to operate.

    The real issue here is that Ubisoft didn’t make it clear what they were selling, and they may even have deliberately misrepresented it. Consumers were either not aware that playing the game required Ubisoft to operate servers for it, or they were misled regarding how long Ubisoft would operate the servers.

    Ultimately I think what consumers are looking for is less like ownership and more like a warranty, i.e. a promise that what they buy will continue to work for some period of time after they’ve bought it, and an obligation from the manufacturer to provide whatever services are necessary to keep that promise. Game publishers generally don’t offer any kind of warranty, and consumers don’t demand warranties, but consumers also tend to expect punishers to act as if their products come with a warranty. Publishers, of course, don’t want to draw attention to their lack of warranty, and will sometimes actively exploit that false perception that their products come with a perpetual warranty.

    I think what’s really needed is a very clear indication, at the point of purchase, of whether a game requires ongoing support from the publisher to be playable, along with a legally binding statement of how long they’ll provide support. And there should be a default warranty if none is clearly specified, like say 10 years from the point of purchase.



  • I applaud the writers of that episode for doing that, but I’ve seen too many episodes/movies where people use alien technology with no indication they have a hard time with the interface, or where a Federation ship outright trades equipment with previously uncontacted aliens, and it just works. Hell, even Trip’s reproductive system is so compatible with an alien’s that she can get him pregnant! And don’t even get me started on how often people just walk up and use a control panel to access sensitive systems without needing to present any kind of credentials.









  • lolcatnip@reddthat.comtolinuxmemes@lemmy.worldthe perfect browser
    link
    fedilink
    English
    arrow-up
    3
    ·
    edit-2
    2 months ago

    whether the software is memory safe depends on the expertise of the devs

    No. Just stop. If a language depends on the expertise of the developer to be free of memory bugs, then by definition, it is not memory safe because memory safety means such bugs are impossible by design. Quit trying to redefine what memory safety means. A program being free of memory bugs does not in any way imply memory safety.





  • lolcatnip@reddthat.comtolinuxmemes@lemmy.worldthe perfect browser
    link
    fedilink
    English
    arrow-up
    9
    arrow-down
    1
    ·
    edit-2
    2 months ago

    I’m very experienced with C++and I still feel like I’m juggling chainsaws every time I use it. And I’ve personally run into into things like use after free errors while working in Chromium. It’s a massive codebase full of multithreading, callbacks, and nonlocal effects. Managing memory may be easy in a simple codebase but it’s a nightmare in Chromium. Tools like AddressSanitizer are a routine part of Chrome development for exactly that reason. And people who think memory management is easy in C++ are precisely the people I expect to introduce a lot of bugs.