Swift is a really cool language. But one thing that blows my mind is that if you ever encounter an "index out of range" error, the (massive) error message that you get doesn't tell you anything about where this error occurred... no line number... no nothing... let a = [1] print(a[1]) Is all you have to do to reproduce the error. The error looks something like that https://pastebin.com/MQV82SaR And gives you no useful…
Thanks for reminding me of why I shy away from Swift and dove into the arms of Kotlin Multiplatform.
> Maybe the friendly default would be to have the symbolicated reports on As a comment just below says, the solution is quite simple: > ensure you have llvm-symbolizer in your PATH or set the environment var `LLVM_SYMBOLIZER_PATH` to point to it
Here is the output with the environment variable set. https://pastebin.com/8M9Dbrgj This doesn't provide anything useful either.
> but now it's just power-user-hostile and considerably more locked down and buggy. Sure, macOS has continued to secure more and more elements of the OS. They have taken a different approach than Windows and Linux, which both keep large swaths of the OS woefully insecure from third-party apps for legacy reasons. But for each and every new lock, there is a key. An incredibly secure OS that gives you the power to contr…
Mac OS does some amazing things for security. An immutable root OS, sandboxing, very user friendly disk encryption. But there are certainly decisions that hold back the platform. Their business decisions have driven most developers away from the App Store. There is a notarization process, but it imposes a burden that many small open source projects can not bear. They don't have an easy way to run untrusted software i…
> Their business decisions have driven most developers away from the App Store.
> They don't have an easy way to run untrusted software in a containerized way (compare Fedora toolbox).
The App Store is the way to run untrusted apps in a containerized way.
> Maybe the friendly default would be to have the symbolicated reports on As a comment just below says, the solution is quite simple: > ensure you have llvm-symbolizer in your PATH or set the environment var `LLVM_SYMBOLIZER_PATH` to point to it
Here is the output with the environment variable set. https://pastebin.com/8M9Dbrgj This doesn't provide anything useful either.
Seems like there's an architecture error or something, the last line indicates you might have an error with the flag:
> zsh: illegal hardware instruction LLVM_SYMBOLIZER_PATH=/usr/local/opt/llvm/bin/llvm-symbolizer swift main.swift
I believe that this long game of Swift being "good for everything" but "better for Apple platforms" will be detrimental to the language. This does not help the language nor seems to bring more people to the ecosystem. Competitors seems to have a combination of: - Being more open-source - Have more contributors - Have a narrower scope Maybe they should consider open sourcing all the tooling (like Xcode) otherwise the…
For folks who want opensource there is always Gnustep and Gorm/ProjectCenter.app.
I don't know about Xcode, but Swift is open source with an active community so if it doesn't work for you then you can definitely bother the Swift Open-Source project with a pull request or a proposal for a language or tooling improvement. You can also have a discussion on the forums or in the bug tracker with fellow contributors. You can also make the change in your own fork and use that. This is exactly how for exa…
Scooby doo meme “let’s see who you really are”. . Apple employee.
Does it matter? Most commits to OpenJdk are Oracle employees and most committees to C# or typescript are Microsoft employees.
> why would I waste my time working on a language that is too tied to the Apple platform This might work the other way round: starting from people familiar with macos or ios development who want to write for other platforms. Then the question becomes: why would a developer learn a different open source language when they can use what they already know. And sure, depending on the context they might still go with Pytho…
> people familiar with macos or ios development who want to write for other platforms. This is a rather small userbase when it comes to enterprise. Especially because Swift will never be as versatile as Python or as efficient as Rust. And then there's also Go, C# and Kotlin with much better tooling.
Xcode gives me such a hard time that I started considering writing in Kotlin for macOS, just to have a normal IDE. We used to have AppCode (from JetBrains) and it was great. I wonder why Apple didn't support JetBrains, after all, it would have been to Apple's benefit.
Can only speak for myself, but I’d love to be able to use Swift elsewhere so I don’t need to drag around a JVM and all the things that come with it (Kotlin) or have to wrestle with Rust’s sematics and disinclination towards old style imperative desktop UI development. Swift isn't perfect of course, but it’s the closest I’ve come to a language feeling “comfy”.
So you haven't heard of Kotlin Multiplatform.
What are your experiences of using Kotlin for modern macOS/iOS development? How's the support looking when Apple releases new XCode?
Here is the output with the environment variable set. https://pastebin.com/8M9Dbrgj This doesn't provide anything useful either.
Seems like there's an architecture error or something, the last line indicates you might have an error with the flag: > zsh: illegal hardware instruction LLVM_SYMBOLIZER_PATH=/usr/local/opt/llvm/bin/llvm-symbolizer swift main.swift
that's not related to the symbolizer thing. It seems to just be part of the "index out of range" crash. I get the same thing without using the symbolizer.
zsh: illegal hardware instruction swift main.swift