It's been about 15 years since I played it, but I recall the writing in Braid being memorably shallow, clumsy, and pretentious (with the grand twist at the end being that they guy who spent the whole game acting like a clingy stalker was actually a clingy stalker this whole time).
The actual story wasn’t anything special, but I thought how it told the story through mechanics was really well done. It wasn’t the first to do that but did it a larger scope than anything else at the time.
I very deliberately did not say anything about my opinion about the quality of writing in Braid (and I think replaying it again wouldn’t do it any favors) ;)
But I do think that the writing was fairly central to the intended experience and design of the game.
Not really, the writing is sectioned away from the gameplay and easy to skip over unread without missing anything relevant to the main event, the puzzles. It's not good but its unobtrusiveness made it easy to forgive. Judging from this trailer the characters will be yapping to themselves and each other during gameplay though, so it had better be well executed, especially if they end up talking a lot.
I think for games like Blue Prince, specifically, it’s not a false dichotomy.
Those are made in tiny teams. You can either spend more time tinkering with the gameplay mechanics and experimenting with the game parts; or you can put on your software engineer hat and make the code better (or, spend even more time to learn how to make the code better in the first place!).
This gets less true with scale of a team, and with 5000 people behemoths you probably should care _a lot_ more about the code; but ROI on improving the code in (relatively! Calling Blue Prince “small” is ridiculous.) small games is very dubious.
Of course programs will be worse when non-programmers are in charge of programming. That doesn't mean they shouldn't but lots of indie game attempts fail because the programmer (educated or not) doesn't have a clue about when to refactor and make sure the design of the system matches the intention of the game. You can only tinker until a certain point, after that you're just creating new bugs by fixing other bugs.
ID software once was a small team and they built complex games by writing tight code which was modular and very clear. Lots of their '3d era' contemporaries failed because their engines were sloppy, complicated, buggy and slow.
A lot of core game logic is presumably Tonda's work. He's a director, not a software engineer. He came into this, many years ago, wondering if the "easy" tools to make a video game meant he could just make the video game he was imagining, and of course the answer is "Yes, but..."
Blue Prince is (an extrapolation of) that first game, but it looks and sounds like competent people worked on it, not like something slapped together by a non-engineer in a week. However while you can hire experts to make "You know, like cool jazz for a mysterious underground area" or "Art that looks thematically like it was sketched, but also feels solid enough that you could lean on it" it's very difficult for software engineers to "just" fix the software to get rid of bugs because what's a bug? Only the puzzle designer knows for sure what they intended.
[[Spoilers! Do not read if you are still playing or might play]]
Is it a bug that "Swimming Trunks" don't let you swim? No! That's a Dad Joke. They're Trunks. Large locked wooden boxes. They're in the swimming pool, and if your pool has water in it, that means they're swimming.
When I picked a time from my near future in Shelter, it didn't work, that's a bug right? Nope. The Shelter cares about game time, not real world time. Make sure you know the date in game.
OK but is it a bug that being in Clock Tower at the Sacred Hour doesn't have any effect? Um, maybe? It seems as though the software doesn't believe clocks repeat, so only the first time will actually work. Or, maybe the second does too? It's hard to say. Try again?
I need food but somehow I keep digging up keys and money. That's a bug right? Nope, probably means you have made a Contraption which changed your dig probabilities.
OK, so that's also why my Door facings are weird even though I put my Compass-based Contraption in a Cloak Room? That one's probably a bug.
Still, "If you draft it quite late" ought to mean my Music Room has the key right? Well, maybe, what did you think "Quite late" meant?
"I thought after a few hours would do it". Huh. Well, maybe. "OK, what about Rank 7?". Rank Nine would be better, but it might be enough, depends. "I still get no key, are you sure this isn't a bug?". The most likely problem is that you've done Music Room. If so the most likely key to wrongly believe you did instead is Vault, although Station is also possible. Check the other locations.
The supported version of DisplayPort in that TV is on par (-ish) with HDMI 2.0; and not enough for HDR 4k120; which is one of the selling points of HDMI2.1.
My understanding is that the HDMI 2.1 port situation on TVs is, weirdly enough, a SoC limitation from a single vendor.
Almost everyone (apart from... Samsung and LG, IIRC) is using MediaTek SoC for the brains for the TVs, and they just seem to be unable to make one that has enough bandwidth for 4xHDMI 2.1.
AFAIK LG and Samsung still handle theirs in-house (and that's why LG was the very first "big" vendor to ship 2.1 at all, and they rolled it out to all four ports even on their midrange TV's in _2019_!); and it's common to see those brands have more 2.1 ports.
This should be getting better in 2025/2026 model years, since it seems MediaTek has finally managed to ship a SoC that does it; but it's ridiculous how long it's taken.
I don’t make the purchasing decision for my employer, but I certainly have to deal with their fallout, so I’ll keep complaining if that’s okay with you.
Well sure, they're iterating between models. But in many cases they're quite literally copy/pasting designs. Any imagined separation between the hardware teams is fantasy based. The comment I replied to is nonsensical.
"They're different even between A19 Pro in an iPhone Air and the one in 17 Pros"
The SoC and I/O blocks are quite literally identical. An A19 Pro is an A19 Pro, aside from binning for core disables. The difference is in the wiring and physical connector on the device which puts a ceiling on the features supported, one of which is 10Gbps. The Air famously includes some new "3D printed" super thin Titanium USB-C port, using the 4 pins rather than the "pro" 9 pin 10Gbps capable connector. The SoC is identical, they just only wired it up for USB 2.0.
I've had multiple USB-C chargers broken like this.
Now, admittedly, "being yanked by a robot vacuum and falling on the ground" is outside the design parameters for a port; but I absolutely had USB-C ports fail in a way that Lightning would have not.
(Not the person you're replying to, but also a "Lightning was a better physical connector than USB-C" weirdo.)
The info that the IRS has from your employer is maybe 5 boxes on your return. Literally takes a few minutes to take the info from your w-2 and put it on a 1040.
If it's so easy, why is the IRS unable to do that? Why must I retype all of the information that they already have? If there's anything they don't have, I have zero issue tying that in myself.
The number and type of people living in your household is not an edge case. It applies to almost everyone, has huge tax impacts, and the IRS doesn’t know.
They can’t. Because IRS IT has been starved, beaten and abused for 20 years. If they had the resources and leadership, all of this could be possible via MOUs and better data access/normalization from the mainframes.
