The Windows 10 right click menu is actually an option within the Windows 11 right click menu, under something like “more options”

I haven’t played it in a while (due to performance issues,) but I remember parrying in Deadlock being really satisfying. The timing was so generous, and led to mind games, fakeouts, mixups and all kinds of shenanigans about when you parry, bait parry, hold parry so the enemy doesn’t know if you’ll parry, training the enemy to expect when you’ll parry before changing when you parry. And because melee isn’t the only focus in combat, it made it a nice skill expression without being a win button.

Last year in February I uninstalled the app on a perfect, 2000-day streak when I got the first whiff of AI; I’m probably never going back

The fact that you used the namespace for cout but not for endl inordinately bothers me

As someone who’s worked on printer firmware before, it makes me really sad that a company can get away with making a consumer decide between getting access to any of the actually useful changes that engineers — who have no say over ink cartridge policy — put effort towards making the best product they could, or not having said ink cartridge policies forced on them.

Don’t forget the barotrauma

I just hope that when “Kakariko” is inevitably said in the movie, it gets pronounced right

My first instinct would be that it would equivalent to putting another celestial body the mass of the earth at the distance from the earth is from each portal. Since gravity is a wave, it, in theory, would affect a region beyond what would considered “around” the portals.

So if you put one portal on the ground, and another 100 meters up, it would be similar to there being a second earth 100 meters from the surface of the earth, experienced by the entire earth (once the gravitational wave propagated.) How that would evolve over time is too complex for my basic understanding of physics, but a simulation of it would be a neat experiment.

Foxy Fnaf 2

From later in the article (emphasis author’s)

Earlier in this article I intimated that many of us are already dependent on our fancy development environments—syntax highlighting, auto-completion, code analysis, automatic refactoring. You might be wondering how AI differs from those. The answer is pretty easy: The former are tools with the ultimate goal of helping you to be more efficient and write better code; the latter is a tool with the ultimate goal of completely replacing you.

When I managed a pool, I remember the Virginia Graeme Baker act being something I was told about pretty early on; it was a prevalent enough of a thing that sometimes trying to start up my spa’s motor wouldn’t provide a clear enough suction, and the motor would shut off for safety. A properly managed pool should never have had this risk.

I would recommend going and watching the pannenkoek video because it is so good.
The quick version is that it has been known to be possible to clip through the wall to get to the door, but Mario has to be in the walking state to open it. Since the floor directly under the door hitbox is all covered by wall, and the part that isn’t covered by wall doesn’t have a floor directly below it, it seems like there’s no way to actually be in the walking state to open it.
However, by abusing an exploit where Mario finishes his turn around animation the same frame he leaves the ground, the transition to the freefall state is overwritten by the transition to the walking state; this lasts one frame until a check is run next frame — which properly puts him in freefall. Timing the turn around right lets you be past the wall and walking, so you can open the door.

The Finals has been my default game — if none of my friends are playing anything else — since it launched

I remember abusing the pause bug, so I don’t actually remember how hard it was without that

A lot of the complexity came from around various scenarios you could be in; my goto whenever people would ask me “Why can’t someone just make printer firmware simple?” is that you could, if you only wanted to copy in one size with one paper type, no margin changes, and never do anything else.

There’s just so many different control paths that need to act differently; many of the bugs I worked on involved scaling and margins. Trying to make sure the image ended up in a proper form before it made it to hardware (which as more complexity, ran on a different processor and OS than the backend so that it could run realtime) when dealing with different input types (flatbed scanner vs a document feeder, which could be a everyday size, or like 3 feet long) different paper sizes, scaling, and output paper. I mainly worked on the copy pipeline, but that also was very complex, involving up to, something like, 7 different pieces in the pipe to transform the image.

Each piece in the pipeline was decently complex, with a few having their own team dedicated to them. In theory, any piece that wasn’t an image provider or consumer could go in any order — although in practice that didn’t happen — so it had to be designed around different types of image containers that could come in.

All of that was also working alongside the job framework, which communicated with the hardware, and made sure what state jobs were in, when different pieces of the pipeline could be available to different jobs, locking out jobs when someone is using the UI in certain states so that they don’t think what’s printing is their job, and handling jobs through any of other interface (like network or web.)

That’s the big stuff that I touched; but there was also localization; the UI and web interfaces as a whole; the more OS side of the printer like logging in, networking, or configuration; and internal pages — any page that the printer generates itself, like a report or test page. I’m sure there’s a lot more than that, and this is just what I’m aware of.

Just what was in the main repo (at least one other repo was used for the more secure parts of the code) was a little over 4 million lines. But yeah there’s a lot of complexity behind printers that I didn’t think about until I had worked on them. Of course that doesn’t mean they have to be terrible, it’s just easier to fall into without a good plan (spoiler alert: the specific firmware I was working in didn’t have a good plan)

I used to work on printer firmware; we were implementing a feature for a text box for if you scanned a certain number of pages on a collated, multi-page copy job. The text box told you it would print the pages it had stored to free up memory for more pages; after those pages had printed, another text box would come up asking if you wanted to keep scanning pages, or just finish the job.
The consensus was that it would be a relatively simple change; 3 months and 80 files changed — with somewhere in the ballpark of 10000-20000 lines changed, — proved that wrong.

They actually don’t have last names; their full names are Mario and Luigi.

This is how I approach these: that square only has a single traffic light, not multiple traffic lights like the prompt is asking for