Skip to content
View WilhelmOks's full-sized avatar
  • Germany

Block or report WilhelmOks

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Maximum 250 characters. Please don't include any personal information such as legal names or email addresses. Markdown supported. This note will be visible to only you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse
WilhelmOks/README.md

About me

Native Mobile

I love developing apps for iOS, especially with SwiftUI. I believe that it's the best developer experience that you can get.

Hybrid/Cross Platform Mobile

I'm sceptical about hybrid/cross platform mobile development like Xamarin, React Native, Flutter and Kotlin Multiplatform.

On the one hand, those technologies tend to die out or be abandoned after a few years. On the other hand, they don't live up to their promises to speed up the development for both platforms, because the theoretical gained speed is counteracted by the quirks of those technologies and the problems with the compatibility to the native SDKs. They never seem to mature enough to be worth using.

In my opinion mobile apps should be written in native technologies, Swift+SwiftUI for iOS and Kotlin+Compose for Android. A great developer experience means fast development and better quality of the end product.

Swift and Kotlin

My favorite programming languages by far are Swift and Kotlin.

Swift combines the performance of low level languages like C++ with the feature set of Haskell and the syntactic elegance and ease of use of JavaScript. It has the advantages of every language and practically no disadvantages.

Kotlin has great syntactic sugar, making declarative definitions and initialization logic of types a joy to use. Sadly it's bound to the JVM and doesn't have custom value types (struct in Swift and C#).

What I love most about Swift and Kotlin is that they make it practically almost impossible to have null-pointer-exception bugs. And both have algebraic sum types, which make it possible to model data safely and elegantly.

Architecture

I believe that the best code architecture for a project is one that is tailored specifically for that particular project. There are no silver bullets. It always depends.

Blog (kind of?)

Some of my thoughts about Swift and development on Apple's platforms, written as short blog-like articles:

https://medium.com/@lensflare

Pinned Loading

  1. JoyRant JoyRant Public

    An unofficial devRant iOS client.

    Swift 8

  2. ModifiedCopyMacro ModifiedCopyMacro Public

    A Swift macro for making inline copies of a struct by modifying a property.

    Swift 35 7

  3. ArrayBuilder ArrayBuilder Public

    A result builder that allows to build arrays with conditions and loops with SwiftUI like syntax.

    Swift 14

  4. ScaledToFit ScaledToFit Public

    Scale up or down a rectangle size so that it fits into another rectangle size.

    Swift 3

  5. VoronoiLibSwift VoronoiLibSwift Public

    Swift implementation of Fortunes Algorithm.

    Swift 8 2

  6. KreeRequest KreeRequest Public

    A lightweight http request helper for JSON REST APIs

    Swift