rezonant

Pressure doesn't mean forcing someone to do something. And I also never said anything about genetics.

Haha yes-- in this case for BoTW to be at the beginning of the timeline, the Rito wouldn't exist yet, as they are only present in Wind Waker and beyond, not that it's impossible for both to exist.

Yeah my point was to downplay how specific this is to Japan, and focus much more on it being a pretty Nintendo specific phenomenon, though you're also right that video games (and other media) as a whole tended toward this sort of thing at the time, whereas now the painful lessons of losing this stuff is more apparent to creators.

It's a fair point, but Nintendo is the only entity that can decide canonicity, and retconning continuity is far from uncommon especially when a franchise transitions from being a single entry to multiple installments.

Nintendo just never did that until the speculation about the topic became noticeable enough that they felt they had to address it (at which point everything was so inconsistent that only the timeline split could reconcile it). And even then, the unified timeline was published years before BoTW, and it adds the wrinkle that... (waves hands) all of the timelines sort of became the same thing.

That sort of hand waving is unavoidable as BoTW has elements from all three of the timelines, it literally cannot be on one of the three legs-- and if it's not, the only other logical place it would fit is before Skyward Sword (meaning an entirely separate ancient founding of Hyrule) or just after the Imprisoning War which would butt up against A Link To The Past. But those can't fit because the Zora evolved into the Rito and BoTW has both.

Never mind the strange notion that a fish people evolved into bird people under the pressure of a worldwide flood... you'd think that wouldn't be necessary or helpful, but hey, Zelda's weird.

Yes, but published very much due to fan pressure, and clearly figured out to match the games rather than being designed up front. Nintendo perhaps more than other Japanese companies intentionally avoids letting existing lore constrain their creativity on new games. That apparently is changing however, as now that Nintendo has successfully launched a cinematic arm they have said they want the movies to be a source of canon that the games will reinforce, a markedly different strategy than they've used previously.

> though picking Angular 2 over React not so much

It sounds like you're coming at this from a perspective of popularity and thus access to engineering candidates with expertise in it which is fair, but speaking as someone who also went with Angular 2 over React during those times, I'm still using Angular and I'm very happy with it from a technical perspective. Yes, it does mean there are less options for hiring, but it has been a positive experience for my team and for me in my own projects to stick with it.

Yep, that's all the voting blocs.

goo-goo g'joob

Within the amount of water lost by a near-median-population nation, perhaps. Not within the amount of water used productively by a near-median-population.

Actually, check out the story of Horizon Zero Dawn.

Only clear to those with a heavy UNIX background-- I understood and correctly interpreted it on first read, but the concept of a "regular file" is a bit in the wonk territory for most users, though the implication on symbolic links is a very practical one that surely lead to the removal (in the implementations where it was removed) of this option, since its very surprising that copying a directory heirarchy would cause symbolic links to become copies of what they linked to, instead of remaining symbolic links in the resulting directory.

> Google's absolutely insane "we're deprecating this, we'll have a replacement for it at... some point, good luck").

Angular 2 came out in 2016, without the two way binding design issues of AngularJS. Google ended support for AngularJS on Dec 31 2021, so there was 5 years of overlap between the two. They even had migration paths that allowed AngularJS and Angular 2 application code to live together from the initial release of Angular 2.

I guarantee the RTMP process on a Playstation 5 is not running as root.

Well, the server just responds with acknowledgement information, the client is doing most of the work and most of the complex parts of RTMP are hand waved and faked by both the client and the server because no one cares about how Flash used to work.

So somewhat unlikely to be able to exploit it but have at it hass.

I'd imagine it'd be easier to exploit the server side, actually.

Imagine if they just let you specify your own RTMP destination. Crazy thought, I know.