Plus an update on Rails 6, Intel's growing adoption of Rust, and the challenge of making breaking changes.

Links:

• Feedback: Academia and Industry — Do either of you have any insights as to how the software development community would view someone with a math PhD, but no industry coding experience as a job applicant? Any advice would be appreciated.
• Feedback: Absurd Abstractions — FYI about wanting `interface` in Python: they are called abstract base classes. Check out the standard library module, abc for that and collections.abc some useful predefined container interfaces.
• Feedback: Breaking Changes — I developed  a niche Python package that has some user following in the network security realm.  I’m at a crossroads though as a change I want to make will subtly break scripts that worked in previous/current versions.  The end result of my pending change  is good for the project but I fear I’ll ruin the workflow of my users.  Other than my github page I don’t know how to query/inform my users of this pending change.  What should I do?
• Ruby on Rails 6.0 Release Notes — Make Webpacker the default JavaScript compiler for Rails 6
• Intel and Rust: the Future of Systems Programming: Josh Triplett — Hear about how Intel is working to bring Rust to full parity with C, building the future of systems programming.
• Altruism Still Fuels the Web. Businesses Love to Exploit It | WIRED — The original well-meaning, geeky architects of the web believed that there was an abundance of altruism in human nature—and they were more correct on this count, it turns out, than many esteemed social philosophers were. But they were too optimistic in overlooking the possibility that corporations would exploit and colonize this new realm. If only we had all seen it coming.
• The Crystal Programming Language — Crystal is statically type checked, so any type errors will be caught early by the compiler rather than fail on runtime. Moreover, and to keep the language clean, Crystal has built-in type inference, so most type annotations are unneeded.
• The Imposter's Handbook by Rob Conery — You've had to learn on the job. New languages, new frameworks, new ways of doing things - a constant struggle just to stay current in the industry. This left no time to learn the foundational concepts and skills that come with a degree in Computer Science.

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

Links:

• RustPython: A Python Interpreter written in Rust
• Apple bans Facebook’s Research app that paid users for data
• Apple restores Google’s own internal iPhone apps after privacy brouhaha — For less than a day, Apple had briefly revoked Google’s 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.
• 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 — as 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’t 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’s 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’s toolbox. But if you tried it you probably know “just” warnings are produced. And sometimes you’d like to have errors instead of warnings, so the build fails hard or something like that. It’s surprisingly easy to do so.