BROADCASTS.com

Mike breaks down the drama around nullable reference types in C# 8.0, and we debate what it means for the future of the language.

Plus a fresh reminder of Apple's absolute App Store authority, and the state of Mike's relationship with the rust compiler.

Support Coder Radio

Links:

• RustPython: A Python Interpreter written in Rust
• Apple bans Facebook\u2019s Research app that paid users for data
• Apple restores Google\u2019s own internal iPhone apps after privacy brouhaha — For less than a day, Apple had briefly revoked Google\u2019s iOS certificate that enabled those private apps to conduct various internal business such as company shuttles, food menus, as well as pre-release beta testing, and more.\n
• Apple Developer Enterprise Program — Get tools and resources to transform your mobile workforce with enterprise-class apps, distributed seamlessly and securely within your organization.
• Apple Is Fighting a Good Fight Against Facebook and Google — The implication that Apple is exhibiting some monopolistic urge to gutshot Facebook and Google makes close to zero sense. The events of this week will not affect their bottom lines, and Apple could have taken much more drastic action to lock down iOS\u200a\u2014\u200aas it has before.
• Nilay Patel on Twitter — Hi, I'm the nagging voice in the back of your head pointing out that it's pretty intense that Apple can simply decide to prevent people from running code on their phones.
• Essential .NET - C# 8.0 and Nullable Reference Types — Nonetheless, as it currently stands, and even after 7 versions of C#, we still don\u2019t have a perfect language.
• Make your next C# project non-nullable — The naming is a bit confusing, because reference types have always been nullable, and that\u2019s the whole problem. The novelty is that they can now also be non-nullable.
• Switch to errors instead of warnings for nullable reference types in C# 8 — Nullable reference types coming in C# 8 are a great addition to anyone\u2019s toolbox. But if you tried it you probably know \u201cjust\u201d warnings are produced. And sometimes you\u2019d like to have errors instead of warnings, so the build fails hard or something like that. It\u2019s surprisingly easy to do so.