thowaway91234

It was always a sewer.

the last one killed me "chef of unecessary meetings" got me rolling

When Kojima announced Death Stranding 2, he joked about rewriting the entire thing after the pandemic because he was trying to avoid predicting the future again. The guy has some kind of super power it seems.

Metal Gear Solid 2 was especially prescient, it's even more relevant today than it was at the time. It seemed like crazy babble at the time but now it's just like, "wow, ok, this all came true wtf".

So this isn't replacing the main implementation? They just funded a new project written in Rust that is compatible?

I love fish. Switch from ZSH+Prezto to just plain Fish and I'm not missing anything and it's way faster. All the servers have bash and I still write bash scripts, but for day-to-day terminal stuff it's Fish all the way for me.

We have developers of various experience and skillsets that come and go, sticking to a subset of language features with minimal magic has made it easier to onboard and get people productive. We have massive codebase, and sprinkling these new sugars around in arbitrary places to be lindmines for them isn't worth it to me. From a business perspective, we're not too concerned about pushing the language forward, we're focused on creating value for our customers - the language is just a detail.

Super Mario is also a kids game and those games run flawlessly with nice graphics and innovative gameplay.

Kids like to play good games too.

whoa, had no idea this existed - looks fantastic thanks for sharing

Delete this before you give someone ideas.

Don't you just level up as high as possible in bioware or bethesda games? Not what I would consider "minmaxing". Skyrim is fun because I can get everything to 100 at whatever pace I choose but there is no "min" involved there for the most part. I haven't played one in a while but there really isn't an incentive to keep your level low in those games. There's only "maxing" with no "min".

Souls games have the community agreed level cap of ~125 for PvP matchmaking, so minmaxing makes sense here - but there barely ever any RNG involved in making a Dark Souls build and you just level up and beeline for the things you want while playing the game "normally" (beating levels and bosses, sunbro'ing to get additional XP along the way, etc..). That said, there's an argument to be made that when ignoring the multiplayer aspect that getting to level 300+ to beat NG+7 is way more fun than minmaxing a 125 build and trying to beat NG+7 that way (my preference, of course).

If there was additional RNG involved with weapon stats or anything like the EV/IV system in a souls game I would never play it, for sure. It's simplicity is what makes it amazing. It's why I hate the bloodgem and chalice dungeons in bloodborne, despite it otherwise being my favorite souls game.

RTS and Tower Defense games I'll give you, since the meta strategy is efficient resource management and maximizing damage to obliterate your opponents with as little resources used as quickly as possible.

As a lifelong rubyist, this is definitely what I would say "useless". Maybe it's just because I've been stuck in Ruby 2.6 ~~hell~~ land for so long but I remember seeing a colleagues leetcode challenge for a job interview that used Ruby 3.1 and he used a bunch of these new syntax sugars and I was really rubbed the wrong way by them. Code the omits arguments is neither more readable (what exactly is getting passed around here?) or maintable (what happens when you have some condition that may apply to one of the arguments, then you just need to unwrap all the "nice" things and do it more traditionally).

The elipsis ... especially rubs me the wrong way because multiple periods either .. or ... denotes range types, but now we have a special case where ... is something completely different. Bah humbug.

They seem nice in clean blog scenarios with trivial examples, but in my experience they are not conducive to writing readable and maintable code.

Thankfully I can just disable their use in my projects (for the most part) with rubocop. All the hip young kids can write their magic code, I'll stick to more straightforward constructs that anyone can figure out.

Minmaxing in almost any game is excruciatingly unfun though, it's not unique to Pokemon. I can't think of a faster way to kill the enjoyment of any game than to try to minmax.

The game was such a technical mess I couldn't get passed it, even though I thought the new gameplay was decent.

and the newest games keep getting worse and worse. barely playable junk and people still buy it like crazy, sad