News for hackers. Stuff that matters.
Re:What's Going Down at the Tiobe Index? Swift, Surprisingly by eyerishcoffee on Saturday April 27, 2019 @06:27PM (#19768016)
Whether there is misunderstanding by the grandparent post or not, in practice there are a lot of people who do just play with ?/! until they manage to get code to compile and then hope for the best.

You can see it all over the place in code people write, posts on Stack Overflow, etc. The Apple Swift book does a poor job explaining the rationale and benefit of using option types.

Re:What's Going Down at the Tiobe Index? Swift, Surprisingly by christoph on Saturday April 27, 2019 @06:43PM (#19768088)
Genuine question - does this not highlight a problem with the language on some level?
Re:What's Going Down at the Tiobe Index? Swift, Surprisingly by shaggyfrog on Saturday April 27, 2019 @06:58PM (#19768152)
If a developer is just fiddling with optional-related operators until the compiler is happy -- in any language, not just Swift, e.g. Kotlin -- instead of actually understanding what they are doing at any fundamental level, that's not a language problem.

I wouldn't want to work with someone like that I doubt anyone else would, either.

Re:What's Going Down at the Tiobe Index? Swift, Surprisingly by geofft on Saturday April 27, 2019 @10:53PM (#19769013)
I would believe it's an education problem, in that we teach things like recursion and local variables (the fact that the same variable can have different values in a nested call to a function) in intro CS classes but we don't really teach how post-NULL languages handle optionals (Option, Maybe, etc.). But it's something that should be part of an effective programmer's knowledge. It's not too unlike buffer overflows—all the people writing UNIX until 1988 were skilled, educated, experienced people, but at the time none of them were really aware just how bad buffer overflows were.
Re:What's Going Down at the Tiobe Index? Swift, Surprisingly by shaggyfrog on Sunday April 28, 2019 @01:00AM (#19769438)
I never learned those in university, so I don’t think that’s a sufficient excuse. Any developer should understand, or want to understand, the fundamentals of the language they are using.
Re:What's Going Down at the Tiobe Index? Swift, Surprisingly by millstone on Saturday April 27, 2019 @07:31PM (#19768308)
It highlights some of challenges of bridging Swift with ObjC APIs.
Re:What's Going Down at the Tiobe Index? Swift, Surprisingly by kitsunesoba on Saturday April 27, 2019 @10:13PM (#19768866)
Fully Swifty UIKit or whatever it is that eventually replaces UIKit can’t come soon enough. As Swift has matured, UIKit/AppKit has quickly become the weakest link in the Apple platform dev experience.
Re:What's Going Down at the Tiobe Index? Swift, Surprisingly by millstone on Saturday April 27, 2019 @11:30PM (#19769163)
Yes, which Apple has done with some success (Toolbox -> Carbon -> Cocoa) but we've also seen how WPF, etc have gone down. The hard challenge is the migration path, and you can't commit until the language and tooling is ready.
Re:What's Going Down at the Tiobe Index? Swift, Surprisingly by pixelrevision on Sunday April 28, 2019 @01:54AM (#19769586)
Optionals when used right really cleans up code that deals with a lot of deeply nested data structures. There is a learning curve though. When you are not used to them so there’s a lot of frustration and sometimes forced unwrapping until it clicks.