{"href":"https://api.simplecast.com/oembed?url=https%3A%2F%2Finsideiosdev.com%2Fepisodes%2Foptionals-are-evil-cC_PNnZ_","width":444,"version":"1.0","type":"rich","title":"Optionals Are Evil..?","thumbnail_width":300,"thumbnail_url":"https://image.simplecastcdn.com/images/80304120-6f39-4345-8f8c-7e654e5ede07/a8c50ee6-0513-4e42-be32-abacacec2ab3/1493514588artwork.jpg","thumbnail_height":300,"provider_url":"https://simplecast.com","provider_name":"Simplecast","html":"<iframe src=\"https://player.simplecast.com/cf12a12b-5770-495d-b41f-e5090591d145\" height=\"200\" width=\"100%\" title=\"Optionals Are Evil..?\" frameborder=\"0\" scrolling=\"no\"></iframe>","height":200,"description":"When and where should optionals be used? What are the advantages and disadvantages of optionals? Before Swift, iOS developers wrote their apps using Objective-C. In Objective-C, programmers could send messages to nil without the program crashing and in some cases was considered a feature. However, sometimes objects were unexpectedly nil and the program would incorrectly execute. Today, Swift uses optionals to more explicitly handle the case when an object is nil."}