Traister101

Oh no

Just kidding I don't care. If anything it makes me happy

It's not really a problem. Frierens demons are explicitly monsters, not in the typical "different species" sense. They gained human language in order to better kill humans, Himmel tries to give a "child" demon a chance and she kills a family.

I love me my "redeemable monster" types, that's why we have stuff like Tensura and other shows where monsters are not inherently bad. In Frieren they are monsters, they exist to kill people end of story. I rather like the simplicity to be honest, it's boring seeing Demon/Monster redemption arcs all the time.

It'll be the end of the series, imo it's a weird decision to make 3 movies. They'd pretty easily get a 8-12 episode season and then a movie for the finale/ending. Hard to say no to monies though I guess idk

I implore you to watch at least the first season (after that plot line is resolved there's not much of a hook to stay engaged).

Shield heros hook is at its core a revenge type story where the revenge is that the people who fucked him over are fucked over in very nearly the same way. The king and princess have their status revoked (they are now commoners) as well as their names changed to Scum and Bitch/Whore respectively. The with fulfilment here is not slavery, (Naofumi goes out of his way to rescue slaves) but getting back at the people in power who ruined your reputation knowingly because they simply didn't like you. Once that arc ends there's not much of a hook, the public sees Naofumi as the only competent Hero (which he's always been), he has great party members and he's slowly overcoming the trauma of being royalty fucked so hard by the royalty (beginning to trust people again). Honestly I cannot see the slave stuff going anywhere but Naofumi finally moving past his trauma and truly freeing his slaves as he no longer is so insecure about being betrayed again.

Is that wish fulfillment? Maybe for you but my kind of wish fulfillment is more along the lines of Konosuba or Tensura.

That is about as misleading as you can get Jesus.

The slavery is werid yes but to TLDR MC is royally screwed over ~~my~~ by the literal royalty and quite literally his only option is to purchase a slave to fight for him (he can't fight). She expects to be abused but he's not a horrible person so she's treated like a normal party member beside one occasion where he orders her to fight a monster dog which she struggles with due to trauma. He quickly resends the order and tells her to run away.

Demi humans (like her) physically grow when they lv up which is somewhat strange but up till now hasn't been used in a way to leer at her or anything like that. This is such a werid show to get into such a fuss about. Have you even heard of Redo of Healer? That shit is fucking vile

Thanks Trump! Now we can genocide people even faster. It's a good thing genocide Joe didn't get elected huh...

Yes? Why would that be surprising

So your writing a game. This game has what I'm going to call "entities" which are the dynamic NPCs and such objects. So these objects are most easily conceptualized as mutable things. Why mutable? Well they move around, change states depending on game events ect. If this object is immutable you'd have to tie the in world representation to a new object, constantly just because it moved slightly or something else. This object is mutable not just because it's easier to understand but there are even efficiency gains due to not needing to constantly create a new version just because it moved a little bit.

In contrast the object which holds the position data (in this case we'll have 3 doubles x, y, z) makes a lot of sense as an immutable object. This kind object is small making it cheap to replace (it's just 3 doubles, so 3*64 bits or a total of 24 bytes) and it's representing something that naturally makes sense as being immutable, it's a set of 3 numbers.

Now another comparison your typical dynamic array type container (this is your std::vector std::vec ArrayList and friends). These are mutable objects mainly due to efficiency (it's expensive to copy the contents when adding new values) yet they also are easier to conceptualize when mutable. It's an object containing a collection of stuff like a box, you can put things in, take stuff out but it's still the same box, just it's contents have changed. If these objects are immutable to put something into the box you must first create a brand new box, and create a copy of the old boxes contents, and then put your new item into the box. Every time. Sometimes this kind of thing makes sense but it's certainly not a common situation.

Some functional languages do have immutable data structures however in reality the compiler usually does some magic and ends up using a mutable type as it's simply so much more efficient.

So what's 0 do then? I'm okay with wacky indexes (I've used something with negative indexes for a end-index shorthand) but 0 has to mean something that's actually useful. Using the index as the offset into the array seems to be the most useful way to index them.

Hah! Elections you think we'll be getting more of those at this rate?

How fancy we talking? The most my fancy IDE tools extend to is like creating functions for me or creating a loop and junk like that. It's not writing any of my code more than autocorrect is writing an essay for me.

Okay so say your testing a brand new rocket engine idea. It uses a fuel nobody has tried to use before. So what you do is you figure out how much energy this fuel has and do some math to figure out how much you'll need to take with you for the typical rocket. You design an engine for this spec or better and thoroughly test it to make sure it's behaving like expected. You eventually mount it to a rocket and make sure in practice it behaves as you expect. Next you put a payload in the rocket and test it again. If at any point things don't behave as expected you have to fix your whole model.

SpaceX struggles to go a launch without their engines destroying themselves. Perhaps they should go back a few steps?