I principally agree with you, it's why I use reddit/lemmy and not 4chan.

But there is a difference, albeit hard to convey correctly through text. But I think some of the extreme responses mentioned are the ones in the banter type. It's a kind of response when someone jokingly says "Star Wars and Star Trek is pretty much the same" and you go "I'll skin you alive" due to the unjust comparison. It sure as hell don't work with strangers, but it can within an community since everyone knows neither party is serious about it. Which is what the original post kind of says that it can work in the right community.

At least Rust compiles down to what is used. I don't know if js has any of that, but at least with rust the final program doesn't ship tons of bloat.

I'm no expert on the grain side, but Netflix had a nice writeup about its power.

https://netflixtechblog.com/av1-scale-film-grain-synthesis-the-awakening-ee09cfdff40b

I also heard that when you use film grain, you should disable the denoising done on the output to properly preserve detail in the encoding. Which depends on the encoder, but should generally be possible on the ones that do film grain.

But it might not be as good for artistic film grain that doesn't fit normal "grain" in videos.

Tesla somehow manages to do well(at least prior to the nazi events). Still at a good price in Norway.

But all other manufacturers have dragged their feet with EVs, and that price cost of starting is large enough that they are in trouble. I'm not a huge fan of China, but they did the investment and are ahead exactly because of that (and crazy subsidies). Being left behind is their own fault imo, and I think that applies a lot to EU as well. Eg. WV.

Code normally works fine after you write it and then hopefully at least test by hand. The new guy 5 years later, which do not fully grasp the extent of his actions, and the guy reviewing the code also not being too familiar with it, will not make sure everything does as intended.

Tests are correctness guarantees, and requires the code and/or the test to change to pass. They also explain how something should behave to people that don't know. I work in a area where there are so many businesses rules that there is no one person that knows all of it, and capturing the rules as tests is a great way to make sure that rules remains true after someone else comes to change the code.

In modern games, I think it's fairly common to have a common 3d skeletons share names. So you can make animations like the one above apply to any character even if they have differences. It doesn't mean that dog extends human, but it may mean that a dog model shares a lot of common "bones", that are used for movement, with a human model.

So when a human animation is applied to the dog, you can see it warp to start position of the animation, move, and then then stop at the end position as a standing human, before warping back to idle animation (when it turns back into the dog shape)

Related, weapons in Destiny also share the same components across weapon types, and bugs have caused one weapon type to be used for another weapon, making funny things happen. Like how a hand canon (pistol) stretches like a bow because it's model got used in place of the bow model at the start of this clip:

https://www.youtube.com/watch?v=0YZa9vv5U0M

"".to_string() probably

I feel this is related, and hightlight this even further, look at all the ways to initialize something in C++.

https://www.youtube.com/watch?v=7DTlWPgX6zs

If you are really lazy, have a look at making an int at around 7:20. It's not horrible that alone, but it does show how many meanings each thing has with very little difference, added on top of years of legacy compatability accumulation. Then it further goes into detail about the auto use, and how parantheses, bracket, squiggly bracket all can be used and help with the mess.