I agree that mipmapping is an optimization, but I also don't really consider it incorrect or misleading to call it a technique for mitigating aliasing - it's a practical technique for doing so. Fair point though, and perhaps I should have mentioned this.
There simply isn't another way to access registers from one 'thread' on another thread without using an intrinsic. You need that to calculate finite differences. For a long time, the only option was ddx()/ddy(). Now we also wave intrinsics, which you couldn't implement yourself either.
Not really. Exceptions usually imply unwinding the stack, and the ability to catch at any point throughout the callstack. Result types are just 'dead' data.
I do actually agree with you. The goal for me was just to understand the connection to CT a bit more precisely, not to imply that it isn't useful. I guess I didn't convey that part very clearly, which together with the tongue-in-cheek title might make me sound like quite a pedant. The post is the culmination of me already knowing Haskell, googling category theory one day, and being utterly confused.
Feels worth mentioning that Learn You A Haskell is about 1/3 the length of the book you mentioned.
I agree that it won't teach you all you need to know to be really proficient with the language, and also wish it didn't omit monad transformers in particular. I still like that it's an easy read, and that I could hand it to someone with pretty much zero knowledge of FP. I used sections of it as a first resource, and then learned the rest by reading documentation, which is how I usually deal with new languages.
I haven't read the book you suggested, so can't comment on the content, but seeing that the first chapter is on lambda calculus makes me a bit skeptical. Perhaps you can tell me, is the book similarly beginner friendly?
No, we can use SM 5.0. It's all DX11. It's not that the framework the game is written in doesn't support such features, we just have no way to bind UAVs for example. What you can do on the CPU is very very limited, while GPU code is completely unrestricted, so we are at the mercy of whatever Unity lets you do on GPU with minimal setup.
Unfortunately true, but also not the experience that most people who continue to play the game have with it. Public instances, especially those in popular worlds, are pure cancer. Anyone who has played more than a few hours will tell you. The reason they are so full of screaming kids is because everyone who isn't one has moved elsewhere.
I very very rarely encounter minors, and hanging out with them makes me uncomfortable too, even having thousands of hours played. Sucks that you had a bad experience, the platform can be a completely different experience if you are brought into it by someone who already knows their way around.
Honestly, the game starts at the point where you meet a group of people you enjoy interacting with and stop visiting public instances. Much easier to get in to with a friend to guide you along the way.