I'm so sorry for your loss.
From my experience with grief there isn't a lot you can do. It simply takes time to process and adjust. Trying to ignore it and power through only makes it harder and longer in my experience.
Try and think about your fond memories and be grateful that you got the time you did. Though I'm sure that means nothing right now.
Talking to a therapist can give you a space to express yourself in a safe and constructive way if you have access to that.
The biggest reason is because it's not work time. End of.
Humans think there's some magic to us that can't be reproduced by machines. But there really isn't.
We're a pattern matching machine with a conscious interface thrown over the top.
Neural networks are really good at finding patterns. Train it on the positions of the planets over a couple decades and it will internally come up with the equations to calculate them and apply those to future and past inputs.
It can come up with equations we don't even know as long as input and output is available for training. Somewhere deep in it's black box it has them.
Art is no different. There's a hidden pattern to art. Something that triggers our brains to react a certain way. You can literally get degrees in the study of it.
Give it enough data and it will learn the patterns.
The problem is it's a tiny fraction of games and users. It's a lot of resources for little gain.
How is it in poor taste?
Trump isn't smart either. He's just a figure head.
The American people's fight has just started. This is far from the only important election.
But chances are they're fucked.
Actually jit languages can outperform compiled languages by using runtime analysis to perform tiered compilation and profile guided optimisations.
C# has made some great strides in this regard.
All the normal optimisations are applied when it is compiled to byte code. Like loop unrolling etc.
Then once it detects the hot paths during execution it can apply even more based on how it is called. It can also do optimisations that aren't possible at initial compile time.
Dynamic PGO it's called. It's a really interesting topic.
Tbh as an experienced programmer I knew exactly what it was straight away. And I don't know rust. I would imagine the others are similar.
The reason that example is simpler is because JSON is literally JavaScript Object Notation.
It's also not the same thing. HashMap have type parameters. So you can only add strings to that HashMap whereas you can add anything in js. Does that code even compile?
You can also do "text".to_string() which simplifies it more.
I feel you're quite inexperienced and once you do more in different languages you'll begin to realise why things are like this.
Rust is a compiled language with static typing so these things are required for the compiler to do its job.
It's also a performance focused language and would blow ts/js out of the water completely on that metric.
Languages are just tools and they all have advantages and disadvantages. You use the right tool for the job.
You can also optimize this a bit.
You can use Activator.CreateInstance instead of reflecting and invoking the constructor.
You can also call MethodInfo.Invoke, you don't need to create a delegate.
Also worth noting that Source Generators have replaced the need for reflection in many cases.
I like using Problem detials
It's fully supported by the .net server pretty much out the box and just seems nice to stick to a standard where possible.
We do like a tipple at the weekend