Did author knows about difference between static and dynamic dispatch? 🤦🏻♂️
Unison stores code in a database.
🫣🤨
Not Electron but yes unfortunately. It uses Ionic that isn’t native, but as declared “native-quality”, that means “mostly looks like native” but that’s not so 🤷🏻♂️. But anyway Voyager is cool. It could be really better with real native UI onboard of course.
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!
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.
Testing interface is not about exactly interface as language’s feature. It’s about testing outer public interface (public API) of you things, looking at it as a black-box and doesn’t matter what happens inside. That's all it means.
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.