I can share my love of Swift - Optional has made null pointer exceptions virtually non-existent. There are occasions where deserialization does result in a nil

I can share my love of Swift - Optional has made null pointer exceptions virtually non-existent. There are occasions where deserialization does result in a nil value where one is not expected, but that's rare. I think this is as massive as garbage collection was back in the day. - The language is in a sweet spot between something convoluted and heavy like Java and something overly simplistic like PHP/Ruby/Python. It's perfect for software development and large code-bases with a low learning curve. - There is no magic (methods, properties, etc). Everything is explicit but not wordy. This may change in the future but I hope it never does. - It's more legible than Kotlin with fewer unnecessary language features. Speaking of which... - It's a simple language and its syntax is straight forward It's not a perfect language: - The package manager needs a lot of work - Extensions can lead to confusion (eg. in the case of conformance to protocols (interfaces)). - I would like an optional garbage collection system for long-running processes (e.g. server-side applications) - I would like it to perform even better You can nitpick syntax anomalies with any language, but a language is defined by how easy it is to scale to multiple programmers, how applicable it is to a problem, how well it performs, how easy it is to read for someone new to the system, how it helps the programmer not commit mistakes, etc. Of all the languages I've written, none has been as successful in all regards as Swift.