@LinkofSunshine So legally... is it ok for you to use whatever means necessary to get the game running? You paid for the game, got a perpetual license, and now the software won't let you make use of it.

@catgirlprostate And that's regardless of whether I would drive myself or used a bus, because both cases hit the same intersection. This wasted 30 minutes of my life doing absolutely nothing every single day for a few years. Because there was never enough money to invest in an overpass

@aidenybai I hated this layout ever since I saw it for the first time and I still do. I just want a paginated list. Not... this mess. At one point I was regularly reading content on one news website. Then they redesigned to use that layout. Didn't read a single article there ever since

@awawawhoami @chromalescence ~5+ years ago he seemed actually pretty reasonable... and then he got political. This truly confirms for me that I was seeing a person I liked become someone I hate, who would likely also hate me

RT @WinRAR_RARLAB: What better way to support the software you’ve NEVER paid for than by buying a WinRAR bag? Do it! We dare y’all!

@uwukko The specifics of why: JS GC in all implementations I'm aware of is a non-moving GC, so you get memory fragmentation but so much worse. Essentially, on average, long running processes with non moving GCs will typically see their memory usage grow with log(time)

@RohanAwhad @wordgrammer For assembly the tool you are talking about already exists and is called "gcc -S filename.c"

@wordgrammer As ridiculously specific as it sounds, actually seems like a pretty good test. It's a problem that we know is solvable, a human or a team could solve it if given enough time (decades), it requires very low error rates, and actual logical reasoning

@SheriefFYI I see what it's trying to say but ends up not saying it and instead does... This

@endermanch @2cabbit The only reason I mentioned wsl is the the post i replied to did. Wsl can just work the same way Linux does because of how isolated it is from the rest of windows

@endermanch @2cabbit My whole point is that the way this design works is that if you just write printf() in your otherwise GUI application, you just can't see the output without modifying the application

@endermanch @2cabbit Use->user You either always have a console and output, or don't have console and doesn't matter what the user does you won't see the output from C stdout

@IsaacKing314 In the simplest case all you need to be able to say that is "under some reasonable assumption, that we can't currently determine that they hold or not, it's proved to be true"

@2cabbit @endermanch (specifically it's determined by subsystem, console subsystem can show stdout, windows subsystem can't)