Electrolytes! (look around you, we are solidly headed there),@retoor Astute! (re layoffs). I had no illusion of any physical fitness at Microsoft (re 20) as there is clearly no mental fitness involved with this product.,@Lensflare It says "safe" but still crashes. It makes me jump through hoops in its "help" with managing memory "For me". My non-swift software doesn't crash b/c of any memory handling... even when the machine runs out of RAM.
Having the runtime engine to support Swift is grossly inefficient. Then top that off with Swift not supporting bit level operations beyond ANDing and ORing...gah
The Swift business of (_) is bizarre, along with the other use of special symbols that feels like ADA. I'm fluent in C, C++ Objective C, Pascal, ObjectPascal, FORTRAN, a half a dozen assembly languages and three machine languages (aka hex code). Swift tries to obscure the "Machine" and remove it from the language construct. That whole "optionals" and "unwrapping" thing it does which has no relationship to reality in the computer itself, drives me nuts. In my mind it is a failure in the model of "not having to deal with memory". They need to learn from MS BASIC circa 1980s```
