3 ms·
I'm much more thrilled about Swift the about Go. Sure Go has a head start in server-side department, but from what I know of Swift I'd much rather write webapps
by cies 11y ago
I'm much more thrilled about Swift the about Go. Sure Go has a head start in server-side department, but from what I know of Swift I'd much rather write webapps in it then in Go.
Many webapps have a kind of "highlevelness" to them, and Swift nicely addresses that with it's features. Go is somehow on a kind of feature diet that's just not my cup of tea. And in terms of low-high-level-ness it I put it somewhere in between Swift and the obviously low-level Rust.
- namelezz 11y agoSwift gives you nice syntax and Go provides you good abstraction for concurrency(channel and goroutines).
- AlphaSite 11y agoHonestly, there are some libraries for swift which are shockingly authentic clones of go's channel + routine syntax. Abstractions like that are not swifts problem. Edit: also, look at https://github.com/apple/swift-corelibs-libdispatch https://github.com/apple/swift-corelibs-libdispatch so those libraries should be portable.
- jug 11y agoYes, this library is listed on swift.org right now as a work in progress for Linux, so Apple is both aware and going to get it done.
- cies 11y agoI understand it more like: Go force one concurrency model on me (like Node.js or Erlang), and Swift is a general purpose language that --over time-- will allow me to use any kind of concurrency model (like C/C++/Haskell/etc.). Oh, and syntax-wise I like both of 'm. I was not referring to syntax much, mostly to capabilities.