• 0 Posts
  • 76 Comments
Joined 1 year ago
cake
Cake day: July 3rd, 2023

help-circle

  • It’s not exactly the same, but Slay the Spire scratched some of the same itch for me. It’s got the same meta-structure as FTL, but the fights use a deck-builder format. It’s really well done.

    One Step From Eden seemed like it should be even better for me, since it borrows the positional strategy stuff from the Mega Man Battle Network games, but I couldn’t get into it. Mostly I remember it being just way too fast. I really wanted to like it, but basically didn’t.

    And yeah, as someone else mentioned, Advance Wars is good, too. The thing that Into the Breach did that Advance Wars didn’t, for me, was that Advance Wars basically depended on the AI being a bit crap so that you could overcome an initial disadvantage and work up to victory. Into the Breach gets around that by making the enemy wholly predictable instead, which is arguably more fun. The only other game I know of that worked that way was an Android game called Auro, but I don’t think that’s playable anymore and I believe the dev has abandoned it. It’s a shame, as it was really well made.

    Other than that… you could try learning Go (aka igo, baduk, or weiqi). It’s a board game with very simple rules, but very deep strategy that emerges from those rules. The main disadvantage is that it’s multiplayer only, but there are puzzles, problems, and AIs you can use to turn it into a solo time killer.




  • I mostly agree with you. The AND was kind of crammed in outside the list too, though; they’d written it as NOT bullet: limit 1, bullet: limit 2, AND bullet: limit 3. Basically I don’t think it’s implausible that they intended it to be maximally restrictive and just screwed that up. I just think that applying the law as though it means that requires interpreting the law differently from how it’s written, and different in a way that harms the defendants, which you previously weren’t supposed to do. Which seems super dumb.


  • I wasn’t suggesting the lawyers or the Justices should have talked about DeMorgan’s law, but rather that it would have been a helpful point for Mother Jones to bring up in the article, to make sure people are on the same page about the logic. You’re right that the notation is probably not helpful though.

    The actual legal argument is pretty simple. The law as written is maximally lenient, but also not very logically consistent (e.g. the redundancy indicated in the article). So it seems like some kind of error occurred in the law-writing process. The question is whether they actually meant to write it as maximally restrictive or whether they screwed up in some other way. That certainly seems like ambiguity (a stance supported by the evidence that multiple courts decided these cases in different ways), and the prior standard was that in the case of ambiguity, you had to interpret the law to the benefit of the defendants, which here would be maximally lenient, and indeed also as written. The supreme court has basically reversed that, saying that you can interpret it as maximally restrictive as long as you’re pretty sure that’s what they meant to say. That’s a very different standard.

    I think this case is maybe the equivalent of that photo of a striped dress that blew up the Internet a few years ago. Nobody thinks it’s particularly ambiguous, but they come to totally different conclusions about what the obvious correct answer is; just because the ambiguity isn’t necessarily obvious to the individual reader doesn’t mean it’s not there.


  • Yeah, I feel like the article should have made reference to De Morgan’s Law in order to explain the two interpretations. That’s the one that says !(A && B && C) = !A || !B || !C, and !(A || B || C) = !A && !B && !C.

    In English, there’s no proper grouping operator, so it’s basically it’s a question of whether you distribute the NOT or the AND first over the list.

    The Justices are saying that the ambiguity is completely resolved by the way the restrictions don’t make sense if you interpret it the other way. But the underlying assumption there is that the laws of this country are logical, free from needless repetition and contradictory requirements, which is a TERRIBLE assumption. Our laws are at best written by a committee of people not very familiar with the subjects of those laws, and at worst written by scam artists who then paid to slip them under the radar and into the books. They’re full of idiotic errors, deliberate sabotage, and absurdities. That’s the whole reason for the thing about the lenient interpretation, and this decision will change that in a way that gives judges a whole lot of power to do more harm.






  • In addition to “format shifting,” which is a well-recognized use case, and game preservation, which is a huge and under-recognized public interest in emulator development, emulators are also used for the development of homebrew software. E.g., there’s a port of Moonlight for the Switch, which lets you play Steam games streamed from a PC using your Switch, letting it serve many of the purposes of a Steam Deck. That’s huge! It would be way less practical to develop this kind of software if you could only test on real hardware. Testing on real hardware is also essential, of course, but testing on an emulator is vastly faster for rapid iteration.





  • I had a similar issue on my Pixel 6, where I’m using Nova launcher. (I know they changed hands and are not great now, but it’s still more usable than the Pixel Launcher.) There the solution was to go into the Apps settings, find Pixel Launcher, and choose force stop, then clear cache, then clear settings. Apparently there was some bug in Android 14 causing both launchers to try to intercept the “recent apps” press, and it caused it to hang like that.

    Obviously that’s not going to be exactly the same issue on your phone, since presumably Pixel Launcher isn’t on there, but maybe doing the “force stop, clear cache, clear storage” on the default launcher on your phone would help?





  • Could still be temperature if the thermistors on e printers read differently–that is, the same setting doesn’t necessarily work out to the same physical temperature on two printers, even if they’re the same model, because the thermistors vary. My suspicion would be that you’re printing a little hot, and the filament is contracting after it’s extruded. On the first few layers it can’t shrink much because of all the material in the middle, but on the vase mode layers there’s nothing preventing it.

    Another possibility is that your overlap percentage between your infill and perimeters is too high. This leads to something that basically is overextrusion, but it’s usually visible as more of a ripple.

    A third possibility is that it’s just the filament.