First game I ever played where I was like “yo, I actively WANT to do the speedrun achievement, and the deathless achievement.” So, first game where I ever did those things. Maybe I’m just crazy, but I found them way easier than I expected.

Also, a prime example of storytelling through music.

I appreciate the “carrot with a bit out of it” icon.

I mean, REST-ful JSON APIs can be perfectly type-safe, if their developers actually take care to make them that way. And the self-descriptive nature of JSON is arguably a benefit in really large public-facing APIs. But yeah, gRPC forces a certain amount of type-safety and version control, and gRPC with protobuf is SUCH a pleasure to work with.

Give it time, though, it’s definitely gaining traction.

#4 for me.

Proper HTTP Status code for semantic identification. Duplicating that in the response body would be silly.

User-friendly “message” value for the lazy, who just wanna toss that up to the user. Also, ideally, this would be what a dev looks at in logs for troubelshooting.

Tightly-controlled unqiue identifier “code” for the error, allowing consumers to build their own contextual error handling or reporting on top of this system. Also, allows for more-detailed types of errors to be identified and given specific handling and recovery logic, beyond just the status code. Like, sure, there’s probably not gonna be multiple sub-types of 403 error, but there may be a bunch of different useful sub-types for a 400 on a form submission.

Slight distinction, though maybe not so much a practical one: it was more “Don’t do that with our weapons, Russia will get mad at us, instead of just you.”

My god, this speaks to me.

Shit, this is a cool idea. I might have to steal this.

That inserter issue has been annoying for so long.

If they get friends, I get friends.

Fuck every last person who gatekeeps the way someone uses intentional game mechanics.

The first one to come to mind is The Core.

Absolutely. Like you say, it just doesn’t happen in large streams, and the threshold is probably a lot larger than you think, since on average maybe 10% of viewers actually participate in chat. The dynamic starts shifting at around 1,000 simultaneous viewers, in my experience, between chat being readable and interactable, and being just spam. That’s still plenty big enough to qualify for partner, and even make a living off of streaming alone.

friendly reminder that the game developer himself said this game ‘needed no female players’" and claimed “some things are made only for men”

I anticipate this game dying in a hot fire.

Article for reference. Unfortunately all the original source (twitter posts and whatnot) seem to have been deleted.

Careful, or the next thing you know, we’ll have lightning powered tumbling sheep evolving, as a defense response.

I remember when Toonami gave it a 10/10 and I agreed wholeheartedly.

I’m probably a lot more willing than the average person to forgive the occasional part that sucked. All games have them, so I try not to hopdbthat against a game that has plenty of non-suck to offer.

Lord knows Sunshine has a few. Fucking Plinko.

Was intrigued until step one of “Getting Started”:

Install Node.js 20 LTS

That’s gonna be a “no” from me.

“Both are valid points to be honest” got me particularly good, for some reason.

I had the exact same question, did the exact same thing, and had the exact same response. EVERYONE does this, it’s infuriating. If you’re going to have a public-facing info page about your project or product, you need to assume that people know NOTHING about it.

Gotta be Breath of the Wild, for me. Taken together with Tears of the Kingdom, the series’ storytelling and immersion has never been better, I think, and as a game, Breath of the Wild was the tighter, more-satisfying experience, overall.

Wind Waker is a veeerrrrrrry close second. I think it’s the most-polished entry in the whole series, in both categories. I’m really not sure what I would change, if given the chance.

MLB 66

I think it’s a fallacy to say that you can or should build an application layer that’s completely DBMS agnostic. Even if you are very careful to only write SQL queries with features that are part of the official SQL standard, you’re still coupled to your particular DBMS’s internal implementations for query compilation, planning, optimization, etc. At enterprise scale, there’s still going to be plenty of queries that suddenly perform like crap, after a DBMS swap.

In my mind, standardization for things like ODBC or Hibernate or Entity Framework or whatever else isn’t meant to abstract away the underlying DBMS, it’s meant to promote compatibility.

Not to mention that you’re tying your own hands by locking yourself out of non-standard DBMS features, that you could be REALLY useful to you, if you have the right use-cases. JSON generation and indexing is the big one that comes to mind. Also, geospatial data tables.

For context, my professional work for the past 6 years is an Oracle/.NET/Browser application, and we are HEAVILY invested in Oracle. Most notably, we do a LOT of ETL, and that all runs exclusively in the DBMS itself, in PL/SQL procedures orchestratedbbybthe Oracle job scheduler. Attempting to do this kind of data manipulation by round-tripping it into .NET code would make things significantly worse.

So, my opinion could definitely be a result of what’s been normalized for me, in my day job. But I’ve also had a few other collaborative side projects where I think the “don’t try and abstract away the DBMS” advice holds true.