Quick Takes: Apple Celebrating Women's Week, The Road to Swift 5, and New macOS 11 Concept

[fairuz]

Here's a silly concept that has nothing to do with what macOS 11 will actually look like.

There won't be a macOS 11.

 

[pppx3]

I think Apple should pay attention to some of these mock up gui concepts. I like the simplicity.
As for where the menu bar sits... tough one. Right now, I don't think Apple have got it right. I remember many years ago, there was an interesting 3rd party program that would allow users to "pull" off menus from the menu bar, turning them into a floating pallet. Another good idea, if you have a big screen.
The bottom line is though, if siri actually becomes a fully fledged way of controlling your computer, then menus become redundant and mouse/keystrokes become less of a requirement - I CAN'T WAIT for this... computers should be operated this way and I believe that this is Apple's direction - this is why they don't care about touch screens. Voice control with hand gestures will be the future of Mac.

 

[73CortinaV8]

literally everything is about selling a product now.

 

[audiomatt]

Apple hasn't put that much effort into macOS in at least 15 years. Good luck.

 

[mspman]

Apple celebrates Women’s Day with picture of guy smirking behind the backs of women.

I know, right! Once you see him you can't look away.

 

[jgbr]

theres been enough of the iOS infection leaching into OSX. OSX needs to cleaned up, core rot removed and stability truly returned. Less new features, more power.

 

[skellener]

I'd take the dark Finder in that image in a heartbeat.

 

[pier]

I've never used Go (the language), but I've heard it's straight up better than Swift. And I've used Swift and don't like it. I think it's good considering all the compatibility they're trying to keep with ObjC stuff, but that's also holding it back severely.

I've used both Go and Swift professionally and I'd say both are great when considering only the languages. I wouldn't matter writing all my stack with either of these languages.

Go cons: dependency management, the lack of generics, and other idiosyncrasies.

Swift cons: the type ****ery with ObjC (which inevitably will have to die) and the fact that it's not yet stable and has no ABI.