I really like ORMs when they are well designed. With a bad API though, it hurts me to use them over a general query string.

I built a small driver for ArangoDB that just uses AQL behind the scenes because it’s so much easier to manage.

Right. Many are hitting with the “it should have been handled in private” line, and it’s kind of annoying. Journalists report on things, and GN did just that. Reported on an issue that has been gaining in public discussion over time. This deserved transparency, and I hope that having it put out there will help LMG/LTT fix their shit. I’m sure I can speak for most of us in saying that we WANT LMG/LTT to SUCCEED. We want to see them produce quality content. But they can’t do that with accurate information right now, despite their public desire to provide that.

LTT: says they want more accuracy, so they build a whole fucking lab for it.

Also LTT: puts bad data into the video anyway because time

That’s literally enough said. It’s not an attack on LMG, it’s pointing out legitimate concerns about LMGs internal processes because these easy to catch errors are getting through all the time.

They test a water block prototype on a card it wasn’t designed for, and then review it as a finished product with the bad data.

It’s a pattern over a long period of time that has been called out by the community. GN is fully right to be putting this out there. Even if you disagree with Steve’s assessment, he’s right to be pointing out things he has concerns with.

Right. I forgot it was on GOG too

I wouldn’t be surprised if this is some sort of intentional fuckery by developers. I mean, the Spyro incident is pretty infamous.

As soon as the initial internal notes were made public I logged out and deleted the app.

I’m not going so far as to delete all of my posts and comments, but I won’t be using reddit moving forward.

Oh no! Anyway…