Beware, what you are comparing vsync off with vrr.

You have four options when it comes to screen refreshes:

• Vsync off, VRR off: you get frames as fast as possible, no latency, but also tearing
• Vsync on: the frame rate gets synchronised with the screen refresh rate. That means, sometimes the game will wait for the screen, leading to a lower frame rate (limited to the refresh rate of the screen) and slight latency, but no tearing
• VRR: the game can lower (not raise) the refresh rate. Compared to Vsync maximum refresh rate it will lower power consumption and do nothing else
• Triple buffering. Needs to be implemented by the game, not by the OS. Provides maximum frame rate and no tearing with minimal latency.

Not yet. Not most of them.

For context: This happened in a German speaking country.

Friend of mine thought it would be cool to have Bladesaw as a gamer tag, but he was a kid and his English wasn’t great, so he spelled “saw” with German phonetics: “Bladesau”.

Until he was at some gaming event where he entered some competition and was called up to the stage as “Blade Sau” (Fat pig).

We can take a few american refugees, but we should limit it to the same measly numbers that the US has been accepting. That would be 50 000 per year.

Over a few millenia we could probably provide refuge for the vulnerable populations in the USA.

1-3-2-4 is actually better.

So first, the context is everything, then the context doesn’t matter, then the context is something else.

So what now? Is it a joke about bullying some creator for stuff he made half a life ago, or does the context not matter when the context is put like that?

Might have been the case 17 years ago. In the mean time Buckley grew up, became a really decent guy and CAD 2.0 is a really good read.

Thinking that loss is still a relevant critique of Buckley or his work just means you are getting old and haven’t updated your prejudices in almost 2 decades.

People posting loss memes almost qualify for an “ok boomer” by now.

India has the same population as all of Europe, all of North America and all of Russia combined.

Tally up the rapes of these two continents and that massive country, and you’ll likely get similar numbers of reports.

It’s a classic case of “by country is not by capita”.

Not saying it necessarily belongs there, just that I saw it there.

Then again it was in a display about the evolution of consumer tech, and there were some newer smartphones there too, so I guess it did fit well into that.

It’s nature’s Beast of ARRGH

I’ve seen a 3DS in the Technical Museum in Vienna.

Nice!

I once had a company give me an assignment that sounded very much like what you are describing. They said I should allocate 10h at once to implement a real-life task that they had and that their developers “already solved”.

At that point I only wrote a handful messages with their recruiter and hadn’t even spoken to a human there. I didn’t even know anything about the team, my potential boss or the project at that time.

I didn’t even answer back, just ghosted them. I’m not going to spend multiple hundreds of Euros of my time just for some assignent to maybe qualify for an interview.

You always have to balance: Do you want the user to have “some” user experience, or none at all.

In the case of image viewers or browsers or stuff, it’s most often better to show the user something, even if it isn’t perfect, than to show nothing at all. Especially if it’s an user who can’t do anything to fix the broken thing at all.

That said, if the user is a developer who is currently developing the solution, then the parser should be as strict as possible, because the developer can fix stuff before it goes into production.

This is literally the difference between me and my wife ;)

The only difference to the standard that I see is that the standard says it should be 1,2,3,4,5, while at least for me it renders as 5,6,7,8,9.

But that’s probably because it doesn’t render as HTML and thus doesn’t rely on HTML to do the numbering.

Yeah, could totally be a regional difference.

I had the same thing when negotiating for salaries too, so it wasn’t just when talking to people, but it was in a more official way as well, and I even got it in my contract like that.

When I was working as a tutor, my contract listed my pay in hourly pay, because I worked varying hours and I was paid by the hour. On my entry-level job my contract was in monthly before-tax pay, but negotiations were with monthly after-tax pay. And my later jobs were all in yearly before-tax pay, which might also have been relevant that way because in some of these jobs I had yearly bonuses and/or part of the payment in stock I got once a year. So with these yearly figures in there, probably it just made sense make everything yearly.

Remember when mail was useful? When you opened the letter box hoping to see a letter from a friend who moved to a different city?

Now mail is just like email. Or to put it differently, email became like it’s physical predecessor.

In Europe people use annual gross salary when they earn enough too.

Monthly after-tax is usually used by lower income people, where low short-term numbers really matter (“Can I make my rent this month?”, “Can I afford to buy/do this small thing this month?”), while annual gross salary is used by people who make a lot of money, where the day-to-day financials don’t matter, but long-term stuff does, and where you also generally have much higher tax pay backs.

I used per-hour salary when I was in university and only worked a few hours per week. I switched to monthly after-tax when I got into an entry-level job that paid quite little, and when I got to higher-paying senior/expert level jobs, I started using yearly figures.