> What's the point of having a status page if it lies ?
Status pages are basically marketing crap right now. The same thing happened with Azure where it took at least 45 minutes to show any change. They can't be trusted.
It's actually the opposite. Calculating an asteroid impact is much easier because it primarily involves basic Newtonian physics. In contrast, the climate is a chaotic system, making long-term predictions far more complex.
I believe the description as a "wall" is not completely correct. Yes, it's a wall as a unpassable obstacle, but the description they gave when walking into it seems more like a field "can't turn around just walk backwards".
The field was just dense enough to stop people from continuing moving forward similar to molasses.
This project might have helped me when I needed to implement a console app that might or not start a web server.
Asp.net is very overbearing (even using minimal APIs) when you want to use other Microsoft utilities like DI, logging or config since it wants to be the main entry of the application.
Never found an easy way to use the host feature with a optional web application where they both shared the DI. Note that this is more a problem with the generic host than asp.net itself.
He already did it with a 1km diameter ball (https://what-if.xkcd.com/12/) and the destruction was terrifying. Please keep him away from these other bigger water balls.
> Some coworkers seem to be having better success but I definitely get the sense they are reading and editing the results carefully.
Yes, you need to consider the AI as if it were a junior programmer that sometimes makes mistakes. I use it for boring work that can be quickly checked. For example, the other day I asked for a 'give me next workday' algorithm based on the code structure I had, and it worked fine.
That's what I've been saying: AI is just a tool that can't yet replace programmers—maybe one day.
I use it for the boring work like generating comments, basic algorithms, API endpoints, and naming stuff. Even with the need to double-check the output, it still takes a load off my brain.
The problem is that Unity is a game engine, not a game framework. That means that any code you do will be following their architecture and using their features. The game logic gets really tight to the engine.
Because the missing device might cause something similar to this crash but instead with a internal mechanism. You really don't want loose stuff around moving mechanisms.
Status pages are basically marketing crap right now. The same thing happened with Azure where it took at least 45 minutes to show any change. They can't be trusted.