This reminds me of my experience as a senior contractor joining teams that seem to enjoy endless discussion. For example, when implementing a new feature using an open-source library or framework they will want to make a prototype of all possible libraries, make a report about each of them, have some big discussions about which to choose, and only _then_ start the real implementation. My advice is always to just pick the one your gut tells you is the right one -- if the prototype works, then that _is_ the implementation and we can stop considering alternatives unless we have a good reason to reconsider them.
If a decision is hard to make, its often because the differences are small, and therefore it doesn't matter much and you might as well decide by dice-roll.
Rust has testing in the standard library -- IMHO Bevy is far easier to test than most game engines because it's "just rust". You can test game logic by starting headless apps, proding the ECS, and making assertions on the results.
For acceptance tests I've dusted off cucumber (after ten years of not thinking about BDD), as I it works great with Bevy
Not OP but I'm currently make a city-builder computer game with a large procedurally-generated world. The terrain height at any point in the world is defined by function that takes a small number of constant parameters, and the horizontal position in the world, to give the height of the terrain at that position.
I need the heights on the GPU so I can modify the terrain meshes to fit the terrain. I need the heights on the CPU so I can know when the player is clicking the terrain and where to place things.
Rather than generating a heightmap on the CPU and passing a large heightmap texture to the GPU I have implemented the identical height generating functions in rust (CPU) and webgl (GPU). As you might imagine, its very easy for these to diverge and so I have to maintain a large set of tests that verify that generated heights are identical between implementations.
Being able to write this implementation once and run it on the CPU and GPU would give me much better guarantees that the results will be the same. (although necause of architecture differences and floating point handling they the results will never be perfect, but I just need them to be within an acceptable tolerance)
Absolutely. As a brit used to waiters and waitresses in the UK and Europe generally leaving me alone until I ask for something, I find the constant fawning interruptions from American service staff cringe-inducing.
A refreshing aspect of US culture is the lack of a historical class system and associated cultural baggage that we have in the UK. So I find it so strange that once you step into a restaurant you are forced into this weird servant/master cosplay where you dictate the server's livelihood based on how you happen to be feeling that day and the resulting whim of your pen writing on the tip line.
Ok so what if I run the website in a VM allowing full execution of ad/tracking code, and then stream the video to a "browser" that blocks out the adverts?
> was clocked to be offset after 5.3 months of running the turbine
.. if the power would have otherwise been generated using non-renewable sources.
But even when (if?) electricity generation is switched to 100% renewable, we will _still_ need to reduce carbon emissions to reduce climate change, so reducing carbon emissions invovled in the creation and maintanence of renewable electricity seems like a good idea to me.
Your contract is legal and enforceable. The parent commenter is just saying that there's no _automatic_ right to work you do in your free time (ie it has to be specifically mentioned in the contract). You could try and negotiate that clause out of your contract though.
* Teams wanting to be a viewer for all kinds of filetypes. Why the hell would I want to view a Powerpoint presentation in Teams? What if I want to chat about the presentation, while viewing the presentation?
* Clipboard injection attacks. Who in the history of the humanity ever thought prefixing "[2:10 PM] Kimble, Richard:" into the URL/API key/thing-you-want-to-copy a colleague just sent you was a good idea? Yes I know you can manually highlight the text and copy, but you're forcing me to do intricate mouse movements that take time, dozens of times a day. I just want to triple-click, cmd+c, alt+tab, cmd+p
> Pretty sure that I’m really the only person that cares about it.
Even if you don't get any useful organic traffic, I find having a technical blog is useful so that when you do go to interviews or submit resumes, hirers can read your blog and quickly establish that you know what you are talking about.