meed
Joined 7 years ago
Joined 7 years ago
Yet Another Fucked Up Attempt To Make C What C Is Not
C is not “unsafe” as in “flawed”: it’s designed to fill certain gaps. Its syntactic stability through the decades - as well as its “minimalism” (for a lack of better word) - are among its most important features.
Personally I have been having an hard time trying to figure out why there’s some part of the industry that desperately tries to change what C is in a way or the other.
...but probably I’m just an old Valley fart. Apologies for the rant.
- cannot even begin to understand why these things lack an important usability feature like MegSafe: there is really absolutely no reason why it cannot coexist with the ThunderBolt I/O (4 TB ports, one MegSafe: charge it however the heck you want).
- find the presence of the castrated TouchBar an offense to users. It seems they just want to shove it down our throats whether we want it or not. Just make it optional: I'm sure that there are certain users out there that love it but every single peer of mine [1] hates the sole idea of something like that.
[1] I'm a software guy in the Valley
Paying 1.2M+ for a palework built with rotting wood in the Bay Area is simply laughable at this point.
And I'm a senior software guy in a big Valley corp.
Probably the real priority here is to find one's "happy place" and stay there as long as it stay that way.