/explore

Click through on any links that interest you or select the planets on the right to continue exploring the Outer Web.
You are here

 preslav.me
Is Swift Playgrounds the Future of Apple App Development? · Preslav Rachev
| | musings.preslav.me
All You Can Feed · Preslav Rachev
0.2 parsecs away

Travel
| | I am a software engineer with decades of experience developing software in Python, Go, and Java.
| | swiftwithmajid.com
WWDC25 wishes | Swift with Majid
4.0 parsecs away

Travel
| | The World Wide Developers Conference, the largest event in the Apple development world, is just around the corner. Today, I'm excited to share my wishes for the upcoming WWDC 25, which is expected to be unveiled in two months.
| | iosdeveloperzone.com
Swift Parameter Labels - iOS Developer Zone
3.8 parsecs away

Travel
| | I am guessing early on in the development of the Swift language the relationship between a function declaration's parameter labels and whether they need to be included in a call was much more forward. Maybe it looked something like this. But then they decided that to make Swift play nice with Cocoa that labels would
| | sookocheff.com
Managed VMs and the Future of App Engine | Kevin Sookocheff
27.4 parsecs away

Travel
| I've been thinking about the transition of App Engine to Python 3 and have come to the conclusion that it will never happen - App Engine will eventually be deprecated in favour of Managed VMs. Let's break this apart to see why this is. First, consider the effort required by Google to develop App Engine. The Python runtime environment was modified to enforce the sandbox of the App Engine environment. To provide a Python 3 environment for App Engine as we know it, the Python 3 runtime would need to be modified with the same restrictions. Even imagining that this would happen for Python 3.4, the effort to upgrade to Python 3.5 would require additional effort by Google to modify the runtime.