They also outperformed themselves before being in a leader position...

I'm definitely dreaming but I think it could be a win-win situation if Apple decided to licence its chips to Valve: the resulting handheld and VR headsets would be power/efficiency monsters and PC devs would finally have a good reason to target ARM, which could finally bring native PC gaming to MACs.

This doesn't feel like anything Apple has done in modern times. The last thing I remember them licensing was the iPod+HP from 2004-2005. Apple barely does enterprise support; they're very focused on selling their products to consumers and I don't think they're at all interested in selling CPUs to others.

Apple waffles and sometimes talks about gaming on Macs, but they lack the commitment that is needed. A lot of people like to buy a game and continue playing it for years, even after the developer went on to something else; or to buy years old games on sale. But you can't expect to run a mac os app compiled three to five years ago that is media and gpu heavy intensive on today's mac os. There will have been mandatory developer updates and it won't work.

Win32 is the only stable desktop ABI... and games need a stable ABI.

The Nintendo Switch already provides >160 million reasons for gamedevs to care about native ARM support, but that hasn't moved the needle for the Mac. Being ARM-based is the least of its problems, the problem is that it's a relatively tiny potential market owned by a company which is actively hostile to the needs of game developers.

The switch is underpowered to the point that most A(AA) games cannot run on it without a ton of effort and compromise, an M chip powered device would be a different story. But anyway it's never going to happen, just daydreaming about a perfect gaming setup...

Only if your table is missing an unique index on that column, which it should have to enforce your assumption, so yeah LIMIT 1 is a code (or schema in the case) smell.

IDs are typically unique primary key. But in my experience, adding LIMIT 1 would on average halve the time taken to retrieve the record.

I'll test again, really the last time I tested that was two decades ago.

That seems like your RDBMS wasn't handling something right there or there wasn't a unique index on the column.

Do you recall what the database server was?

Yes, I was using Mysql exclusively at the time. I don't recall which version.

I also tested this once years later when doing a Python app with sqlite. Similar result, but admittedly that was not a very big table to begin with.

I am meticulous with my database schemas, and periodically review my indexes and covering indexes. I'm no DBA, but I believe that the database is the only real value a codebase has, other than maybe a novel method here and there. So I put care into designing it properly and testing my assumptions.

You should use the DB explain or equivalent command to spit out the query plan, limit 1 shouldn't change anything in your case, if it's not the case you should file an issue, it's pretty much 101 of query optimization.

That would be a reportable bug. Of a pretty high priority.

You are certainly doing something wrong if that's true.

I'm curious, can you demo this?

I'm curious as well to see if this still holds up. I'll try this week.

They would obviously fix it pretty quick if you reported something like that, the still open github issue is about pure styling/readability issue...

Try "go to implementation" in place of go to definition.

The Belgian section has no french language articles, they still need to work some things out but I welcome the idea.

It's a cutoff delta, you have to subtract it from the "preliminary" qualifying time.

Doesn't look true, I inputed the times in an age grading calculator and 39 cutoff time was easier than 44, even if it's not very accurate I doubt it's "much easier".

Most of the time it's not the people who created the link who are going be annoyed with the broken link...

Same experience here with a 2024 EX40, happy I did some research before buying (EX30 was looking nice at first). The EX40 is just another iteration of a mature platform, while the EX30/90 are new and still full of bugs apparently... It shows in the central console that looks dated but at least it works and I still have buttons for basic functionnality.

2023 C40 (same platform) here, similar experience. I'm happy with my purchase.