Re:On Apple's Love Affair with Swift
by _ph_ on Saturday August 11, 2018 @09:24AM
(#17739575)
I can understand the need to create a new programming langauge, but as the previous poster wrote, they rather recreated all the complexity of C++, instead of a more lean language. Also, Swift seems to suffer from overly static typing in its object oriented approach - which defeats the idea of object oriented programming.
[ Parent
| on HN ]
> they rather recreated all the complexity of C++
I find that this assertion holds about as much water for Swift as it does for Rust, Swift is not even remotely close to C++'s in terms of complexity, and that's with building in mechanisms for performant memory safety, a concept which C++ literally just shits on to this day and for the foreseeable future.
Swift is a really approachable language, it’s core features are simple and the code is very readable. You can write any app without having to use generics, extensions, protocols, more esoteric enum features, etc, etc.
But once you learn to use the more advanced features, your code just gets easier to write and maintain. I enjoy that I can pickup new language features in Swift one at a time, figuring out where each adds its best value, and occasionally refactoring to take advantage as part of my ongoing efforts to minimize code debt.
It’s hard to take seriously the idea that swift and c++ have equivalent complexity if you have delivered products using both languages.
It’s not even close. Swift is (still) minimalist by comparison to C++.
Swift is complex, but it is not C++-complex. C++ is in the completely different league.
Re:On Apple's Love Affair with Swift
by pertymcpert on Saturday August 11, 2018 @07:54PM
(#17742184)
That's extremely hyperbolic. I've worked on multiple C++ FEs and it's orders of magnitude more complex than Swift.