←back to thread

612 points dayanruben | 1 comments | | HN request time: 0s | source
Show context
tux3 ◴[] No.42899950[source]
The goal for Swift should (and seems) to be to gradually separate itself from XCode, which is holding it back from its ambitions.

XCode has been compared to many things, but at 3.1 stars on the App store, one must find that it is still slightly overrated.

replies(4): >>42899981 #>>42901466 #>>42902607 #>>42906323 #
dlachausse ◴[] No.42899981[source]
Swift hasn’t required Xcode for several years now. It has robust command line tooling and a VSCode plugin.

https://www.swift.org/documentation/articles/getting-started...

replies(2): >>42900031 #>>42900176 #
airstrike ◴[] No.42900176[source]
Despite being terrible, the last time I checked, the experience in Xcode was somehow still meaningfully better than with the VSCode plugin
replies(1): >>42901419 #
rescripting ◴[] No.42901419[source]
What don’t you like about the VSCode plugin?
replies(1): >>42903491 #
jitl ◴[] No.42903491[source]
For me it just spins forever and never manages to do any LSP things
replies(2): >>42903767 #>>42904388 #
myko ◴[] No.42904388[source]
Pretty similar to the Xcode experience, then
replies(1): >>42904666 #
1. jitl ◴[] No.42904666{3}[source]
I find Xcode completion and especially doc lookup pretty good. It’s not as good as being able to jump straight into framework source code like with Android Studio but better than pretty much anything in VS Code in any language.

That is, as long as there’re no type errors in my code… once I get a little too creative in SwiftUI all bets are off.