4,326 karma · joined July 12, 2018
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.
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.
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.
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.
Seems like people who complain are unaware that anyone with a modicum of karma can flag and down vote.
Regarding the former, there's no normal Copy button so presumably this just copies the content of the article. Not sure why it needs to be clarified that its for LLMs.
> and at the same time seemed to have lost the ability to centrally disable training on prompts for your entire organization
vs
> Vibe (Teams): Administrators can disable data training usage for the entire organization.
Is the document out of date? Or did Mistral reinstate this ability after the fact? What's the story here? Others seem to be stating they have and have had the ability to opt out of training centrally for a long time.
EDIT: Oh, it is addressed just a bit hard to find with all the opt in/out explanations: https://news.ycombinator.com/item?id=49549102
So there's no sense treating it like the community has forsaken you.
Also worth noting simple horizontal centering of divs was never a problem, margin: auto was defined in CSS Level 1 in 1996 [1].
It was vertical centering that took a very long time to crack, which really became trivial with Flexbox which was first drafted in 2009[2] but became available unprefixed in browsers between 2012 and 2014 [3] about 13 years ago.
[1] https://www.w3.org/TR/REC-CSS1-961217
[2] https://www.w3.org/TR/2009/WD-css3-flexbox-20090723/
[3] https://caniuse.com/flexbox
Subnote: I'm not counting the display: table hacks.