3 ms·
Yeah it’s kind of bizarre that after writing everything leading up to that, the author would still frame the ObjC folks in that way. Like, this or that eng. was
by asimpletune 6y ago
Yeah it’s kind of bizarre that after writing everything leading up to that, the author would still frame the ObjC folks in that way. Like, this or that eng. was so brilliant with their hack, but all those obj-c eng. who advocated boring but stable solutions all along were just curmudgeons with no helpful advice.
- quasse 6y agoThe problem from the author's perspective is that the Obj-C "curmudgeons" were proving the right solution to save the app (drop Swift and cut losses + go back to a functioning language) but not the careers of the people who had gotten them into this terrible situation.
- andrewprock 6y agoThis perspective is reflexive. The "ObjC curmudgeons" didn't feel like the adventures that the "Swift zealots" were generating helped their careers in any way.
- jonny_eh 6y agoSounded like a "both sides" analysis, where the assumption is that both sides in a disagreement must share blame.
- entropicdrifter 6y agoThe Middle Ground Fallacy
- CoolGuySteve 6y agoIt's the developer equivalent of "support the troops or get out of the way!" Don't ask why, just do or die. But yeah, I would have been pissed off if I was put in this situation by myopic upper management.