• 4 Posts
  • 19 Comments
Joined 1 year ago
cake
Cake day: June 15th, 2023

help-circle



  • Totally fair! They did a good job of making the main storyline playable as a solo player, but the core gameplay loop is still unmistakably MMO-style and not to everyone’s taste.

    I love that song in particular because (very minor spoiler) it works both as background music and as diegetic music. In the story, that boss is trying to entice you into going permanently to sleep and living in a dream world where you’ll achieve all your goals and desires, while becoming her meat puppet in the real world. When you’re playing the game rather than watching it with onscreen lyrics on YouTube, you are only sort of half-listening to the song while you focus on the battle, so you don’t realize right away that the battle music is the boss singing to you to seduce you into her flock even while you’re fighting her.






  • I think this is a more subtle question than it appears on the surface, especially if you don’t think of it as a one-off.

    Whether or not Scientology deserves to be called a “religion,” it’s a safe bet there will be new religions with varying levels of legitimacy popping up in the future. And chances are some of them will have core beliefs that are related to the technology of the day, because it would be weird if that weren’t the case. “Swords” and “plowshares” are technological artifacts, after all.

    Leaving aside the specific case of Scientology, the question becomes, how do laws that apply to classes of technology interact with laws that treat religious practices as highly protected activities? We’ve seen this kind of question come up in the context of otherwise illegal drugs that are used in traditional rituals. But religious-tech questions seem like they could have a bunch of unique wrinkles.














  • Answering my own question: My systems do zero-downtime deployment. Some of my services are managed using ECS and some using custom deployment scripts.

    It’s interesting that people mostly focus on the mechanics of launching the new code. To me, the interesting thing about zero-downtime deployment is what happens while the release is in progress, when there will be a mix of the old and new code versions accessing the same resources (databases, microservices, etc.) at the same time.

    For example, you don’t want to just drop a previously-mandatory column from a SQL database: even if your new release no longer references the column, the new code will break if you deploy code before updating the database, and the old code will break if you update the database before deploying code. Obviously there are ways to do this kind of thing (roll out the change in small backward-compatible steps) but they’re extra work and can be easy to get wrong even if you’re using ECS to launch the code. Whereas, if you’re allowed to take downtime, you can do it all in one step without worrying about mixed-version environments.



  • Wish people wouldn’t do this, though I do understand the motivation. IMO it ends up punishing other Internet users (who are the ones getting value from year-old comment threads) vastly more than it punishes the owners and employees of Reddit, Inc. (who get most of their value from people participating in active discussions and seeing ads along the way).

    The end result is that you search for “how to fix a broken curtain rod” on Google and the search results are full of comment threads like

    Anyone know how to fix a broken curtain rod?
        [deleted]
            Oh, that's a good idea. How do you unscrew the end if you do it that way?
                Hello! I have removed my comment from reddit because I don't like the
                way they're running their company. You can find me on Lemmy.
                    Thanks! That worked.