Huh. I was expecting that comparison to go the other way given Go's notorious verbosity in terms of error handling, generics etc.. Maybe people compensate for verbosity in one area by being more concise in others (though that doesn't explain e.g. APL).
Or, I suppose you could say that Go is semantically verbose (explicit error handling, no/low use of generics, no operator overloading), but syntactically concise (short variable names). Swift is the opposite, being semantically concise (extremely heavy use of generics, default arguments) but syntactically verbose (labeled arguments, English-like clauses, result builders).
And never mind that cognitive load that comes from managing the use of symbols that are the "same symbol" modulo something the typeface. Trying to read something like
"Little b equals Fraktur Bold Capital B divided by (q times Cursive Capital B) all over Gothic Italic B", blah, blah... then throw in the "weird little squiggle that looks kinda like a 'p' but not quite". It's insane.
My most-used programming language is Go, but I’ve been writing mainly Swift for the past year or so. While there’s a lot I like about Swift, its verbosity leads me to waste an inordinate amount of time pondering what the correct verbiage ought to be, and I often miss Go’s more terse, often single-character naming convention.
>_POSIX_C_SOURCE
>TIOCGWINSZ
>SIGWINCH
>TIOCSWINSZ
Jesus christ, this whole fashion among the C and linux people focused on writing shorter, but unreadable names is really terrible habbit
I hope they're also working on redesigning the MacBook Pro to feature a display without a notch. I'd buy that instantly.
The only hiccups I ever have are resolving Swift result builder types…perhaps SwiftUI is just a big ploy to burn up all the extra CPU cycles.
They also did move the Magic Keyboard and Magic Mouse to USB-C.
Only for the bundled peripherals, it seems. The Apple Store now only lists the full-size Lightning keyboard without Touch ID in white, which is even worse than before when you could get various permutations of tenkeyless, Touch ID, and black.
Suppose you're doing gig delivery. You're delivering to two customers in the same neighborhood on the same run. You drop the first order, take your photo of the drop, and the app spins. It's waiting for the photo to be delivered before it moves on. You can't get directions to the next customer until the app moves along. Why can't it just take the photo, take the text description, and hold that until service is better? Just give the driver the map, and upload the other stuff when you can.
I have similar issues with every app. It seems like every user interaction, every button press requires a round-trip to the server before the app moves to the next step. There's no reason for this. I wager that every app can keep its UI and the user's data locally, and send and receive teensy data updates.
But all "the best" software development employees (that they claim their hiring process hires) in these companies can't seem to work that out.