Done!

Ok, understood, thank you.

I’m not sure is it sarcasm or that’s really not bad short description? 🤔

Trying to reduce compilation time, reconfiguring underlying cargo’ build-ctx or just riding off the context and using only build-plan and metadata by host cargo & rustc in the cargo-playdate tool.

Nope. This little neat feature mainly is just necessary part of bigger one - const-generics with const bounds.

I just don’t care, I’m only 40 years old, it’s a kid’s age.

Did author knows about difference between static and dynamic dispatch? 🤦🏻‍♂️

Unison stores code in a database.

🫣🤨

It’s to teach AI more properly?

I love ligatures and Fira Code (retina) is the best and absolutely comfortable for me.

Ah! 😣 Why not nest or self-hosted pijul!?

More langs for the God of Langs!

Kind of destiny 🤦🏻‍♂️

I started programming when I was in primary school. And I liked it very much, even though I didn’t understand much even then. But it was impossible to stop and here I am writing this after about 30+ years.

What exactly attracted me - my father soldered a Russian clone of the Sinclair ZX Spectrum, showed me a couple of games loaded from a tape cassette, and I was curious how it works.

More than ten years ago, I was a team-lead in a game development company and during another crunch I was very overloaded with tasks, including a code review. And of course, I missed some things. We optimized the game, which in general did not do 30 fps on the target machine with minimum requirements, and the target was at least 40 fps. During the month, we jointly optimized everything so that we were able to achieve almost stable 40 frames, but this was not enough and periodically there were drawdowns up to 15-20 fps. Everyone is in panic, there are no ideas, we’re optimized everything.

No, I understand that there is no optimization limit apriori, but I mean an adequate opts without rewriting everything to assembler specifically for all supported architectures.

So, one night I looked into the event loop initialization and found that the initialization happens twice. Twice. Two parallel event loops. That is, two parallel cycles of logic and state updates. That night, by deleting one line, I optimized the performance of the game by more than 100%. 🤦🏻‍♂️

I investigated and found out that this line of secondary initialization was left by junior “for debugging” and forgotten in the crunch. And I missed it on the review.

I’ve keep this story a secret all these years. And now I’m not revealing names. Otherwise, it can have a dramatic impact on the careers of many.

I’m sure we need a bot for lemmy or entire fediverse that will search posts like this 👆 and do comment with “normal” link. That will be great. I saw something like that in the Masto for YouTube.

I have to suggest to try benchmark-games like this:

• https://sschakraborty.github.io/benchmark/index.html
• https://benchmarksgame-team.pages.debian.net/benchmarksgame/index.html ❤️‍🔥

Also [email protected] gamedev in Rust-lang.

I see. I suppose that exa is abandoned for two years or more and perhaps there’s no connection with maintainer. So then fork.

Hmm 🤔 something new for me. I’m in love with exa. What’s wrong with that?

“Almost dead” link.

This website’s certificate expired yesterday.

Here’s always alive link.