4 ms·
Good point. Lately I have been learning Swift and SwiftUI and application sizes for macOS and iOS tend to be very small. Except for not being a lazy evaluatio
by mark_l_watson 7y ago
Good point.
Lately I have been learning Swift and SwiftUI and application sizes for macOS and iOS tend to be very small.
Except for not being a lazy evaluation language, Swift development feels a little like Haskell, which to me is a good thing. I learned Swift back when TensorFlow for Swift was released and having one language that is adequate for many types of applications is useful. That said, when I want to be happy programming I try to use Common Lisp or Racket. I am approaching my 40 year anniversary for using Common Lisp and there is definitely something really great about deep familiarity with a language and it’s dev tools.
EDIT: also +1 for FreePascal. Someone hired me to use FreePascal on a project several years ago. Good language, small learning curve, and small and efficient applications. On small application sizes: I recently discovered that if you build SBCL Common Lisp from source, there is a compression option for building standalone applications that you can enable that gets application size down to about 15 MB, with application startup around 75 milliseconds.
- didibus 7y agoInteresting, but I wonder if Swift and Swift UI isn't cheating, since I'd assume most of their runtime is already present on iOS and macOS for them to link against. This is also often true of all these "native" solutions. It's more that the toolkit and the runtime is bundled into the OS they target, where as Electron or Java apps bundle absolutely all their dependencies including their own runtime. Though with Java, I think you could assume the user would install those separately, and you could just to use the existing ones.