cubic

My least-effort solution to most of these issues is to be storing hard copies of the password to my primary email in different places and using 2FA.

Then if my password manager does get nuked or compromised, I can "restore" my accounts by using the "forgotten password" feature for most places. If I get trojaned, what are they really going to do with my accounts? The majority of things of importance are behind 2FA anyway, and I'm not a public enough figure that any of my data that isn't is of any importance anyway.

The primary reason for calling it an abomination is that if they actually plan on having this used (especially if by other people) it will spectacularly break the moment Chrome decides to make their quirks mode more strict.

It's a fun hack, although not exactly very unique. See also the very old by now "Website in a PNG file" concept, which does the exact same thing: https://gist.github.com/gasman/2560551

> Forcing SBMM in all cases just seems like it's meant to protect n00bs from getting crapped on but isn't this coddling players?

Most people want to have fun when they play. Players consistently getting curbstomped and having no reliable avenue for improvement is a good way to create a game with terrible player retention. People don't stay around to suffer through game after game just because they really like ninja.

"Ranked" implies a competitive, high-stakes mode, which drives people who want a relaxed game (i.e. one where they _won't_ repeatedly get curbstomped) to naturally gravitate away from a game described as such. You may think that's stupid, but you can't really fight basic human psychology.

Don't forget, "n00bs" are people too.

And many people prefer to not play games where they have to suffer through however long a match takes in a hopeless effort to maybe not lose _that_ much.

I would vastly prefer if every match I play makes me at least _feel_ like I have a chance to win if I try hard enough, than have a large percentage be obvious losses leading only to frustration and waste of time.

Oh, absolutely. I'm actually pretty sure I can count on one hand the amount times I've seen any of my friends / clan mates who consistently play pvp modes blame themselves for a loss. They are very quick to assert that they're "carrying" when they win, though.

I have seen some of their recordings, the difference in performance between them and their teammate is much lower than they think.

Exactly. The issue they seem to be having is that they finally have to experience the game like _the rest of the playerbase_ does.

I have played games without SBMM (Destiny 2 recently switched away from it in certain game modes) in periods when the sweatiness is particularly high and people join as premade teams to stomp some noobs. Let me tell you that as a casual PvP player, it absolutely ain't fun.

I'd say it depends on your definition of "production ready". The APIs are likely to be stable and well supported, but the current library does suffer some culture clashes, as they're mostly just done with Swift's Objective-C interop. A lot of the APIs are somewhat annoying to approach due to them being designed with Objective-C in mind. Most standard library APIs will be rife with implicit optionals and require extra type checking, especially if you're implementing delegates.

In particular, dealing with Core Data can be a holy mess with Swift because every single property on a Core Data object is dynamic and implicit optionals. Unlike Objective-C, which will happily pretend like nothing has happened (in many cases), Swift will explode quite spectacularly if you try to operate on nil values, and implicit optionals lets that happen without throwing type errors. Either be very careful with marshalling accesses to Core Data objects, or test thoroughly with different data patterns. Last thing you want is your app crashing because someone filled in data in your app that leaves a property set to nil.

I'd expect some resistance (on top of the "I need to learn a new language" part), and some swearing about all these "if let"'s or "I thought Swift meant no more null pointer exceptions!", but it's perfectly doable.