• 24 Posts
  • 182 Comments
Joined 1 year ago
cake
Cake day: July 17th, 2023

help-circle




  • My main nit is that Rogue Incursion is hamstrung by how well one can tolerate existing in a tense VR setting for extended periods of time. (For me, I felt insane after taking my headset off, like I hadn’t blinked once in 30 minutes.)

    Yyyyeeeaaaahhh, I probably couldn’t go 3 minutes 😅 I’m a big 'ol wuss and I just can’t do horror games, even though I absolutely love horror movies and the Alien franchise – I get so immersed in games that survival horror stuff is just a nope for me


  • They targeted gamers.

    Gamers.

    We’re a group of people who will sit for hours, days, even weeks on end performing some of the hardest, most mentally demanding tasks. Over, and over, and over all for nothing more than a little digital token saying we did.

    We’ll punish our selfs doing things others would consider torture, because we think it’s fun.

    We’ll spend most if not all of our free time min maxing the stats of a fictional character all to draw out a single extra point of damage per second.

    Many of us have made careers out of doing just these things: slogging through the grind, all day, the same quests over and over, hundreds of times to the point where we know evety little detail such that some have attained such gamer nirvana that they can literally play these games blindfolded.

    Do these people have any idea how many controllers have been smashed, systems over heated, disks and carts destroyed 8n frustration? All to latter be referred to as bragging rights?

    These people honestly think this is a battle they can win? They take our media? We’re already building a new one without them. They take our devs? Gamers aren’t shy about throwing their money else where, or even making the games our selves. They think calling us racist, mysoginistic, rape apologists is going to change us? We’ve been called worse things by prepubescent 10 year olds with a shitty head set. They picked a fight against a group that’s already grown desensitized to their strategies and methods. Who enjoy the battle of attrition they’ve threatened us with. Who take it as a challange when they tell us we no longer matter. Our obsession with proving we can after being told we can’t is so deeply ingrained from years of dealing with big brothers/sisters and friends laughing at how pathetic we used to be that proving you people wrong has become a very real need; a honed reflex.

    Gamers are competative, hard core, by nature. We love a challange. The worst thing you did in all of this was to challange us. You’re not special, you’re not original, you’re not the first; this is just another boss fight.












  • I dint know many OO languages that don’t have a useless toString on string types.

    Well, that’s just going to be one of those “it is what it is” things in an OO language if your base class has a toString()-equivalent. Sure, it’s probably useless for a string, but if everything’s an object and inherits from some top-level Object class with a toString() method, then you’re going to get a toString() method in strings too. You’re going to get a toString() in everything; in JS even functions have a toString() (the output of which depends on the implementation):

    In a dynamically typed language, if you know that everything can be turned into a string with toString() (or the like), then you can just call that method on any value you have and not have to worry about whether it’ll hurl at runtime because eg. Strings don’t have a toString because it’d technically be useless.


  • Everything that’s an Object is going to either inherit Object.prototype.toString() (mdn) or provide its own implementation. Like I said in another comment, even functions have a toString() because they’re also objects.

    A String is an Object, so it’s going to have a toString() method. It doesn’t inherit Object’s implementation, but provides one that’s sort of a no-op / identity function but not quite.

    So, the thing is that when you say const someString = "test string", you’re not actually creating a new String object instance and assigning it to someString, you’re creating a string (lowercase s!) primitive and assigning it to someString:

    Compare this with creating a new String("bla"):

    In Javascript, primitives don’t actually have any properties or methods, so when you call someString.toString() (or call any other method or access any property on someString), what happens is that someString is coerced into a String instance, and then toString() is called on that. Essentially it’s like going new String(someString).toString().

    Now, what String.prototype.toString() (mdn) does is it returns the underlying string primitive and not the String instance itself:

    Why? Fuckin beats me, I honestly can’t remember what the point of returning the primitive instead of the String instance is because I haven’t been elbow-deep in Javascript in years, but regardless this is what String’s toString() does. Probably has something to do with coercion logic.