Live data from Hacker News

Pushing Swift to the Server

skilled.io

21–30 of 109 posts

Re: Pushing Swift to the Server

#21
post #5

Is Swift on the server a good idea? I don't own (or plan to own) a Mac. Does Apple support cross-platform tooling? I honestly don't know, but given their history, my default assumption is to be skeptical. Why would you choose this over Go or Rust? (Rust is totally sweet for server dev, and I've spun up a few Rust servers for things.)

For the clever design of the language: coding with optionals is a breeze, it defaults to thread-safe reference counting, a cleaner syntax (IMHO only), .... .

For the unifying potential of the language: swift on the server (currently linux / freebsd limited), swift on mobile (Google seems to be moving in this direction too), swift on the desktop (macOS only).

Re: Pushing Swift to the Server

#22

Wow. That "same language connected by an interface schema would have prevented Mars mission loss" thing is a really thin stretch.

Exactly. I'm a fan of Swift on the server, but this is the best they can do with marketing?

It's still early, 2017 will be exciting times with Swift 4.

That's where we are coming to share more of SSS topics in https://www.facebook.com/ServerSideSwiftCommunity/

Re: Pushing Swift to the Server

#23

Wow. That "same language connected by an interface schema would have prevented Mars mission loss" thing is a really thin stretch.

Yeah, the Mars mission loss is also really well-worn at this point. I've heard this example in contexts ranging from cross-org communication, to software APIs, and unit checking (as in SI, USCS, etc.). Now I can add "language X is better than language Y" to that list!

Re: Pushing Swift to the Server

#26
post #5

Is Swift on the server a good idea? I don't own (or plan to own) a Mac. Does Apple support cross-platform tooling? I honestly don't know, but given their history, my default assumption is to be skeptical. Why would you choose this over Go or Rust? (Rust is totally sweet for server dev, and I've spun up a few Rust servers for things.)

Go and Rust are fine for some use case. Swift is fine for iOS and macOS developers as they are all backed by strong communities.

Roadmap for Swift: http://researcher.watson.ibm.com/researcher/files/us-lmandel...

Re: Pushing Swift to the Server

#27
post #5

Is Swift on the server a good idea? I don't own (or plan to own) a Mac. Does Apple support cross-platform tooling? I honestly don't know, but given their history, my default assumption is to be skeptical. Why would you choose this over Go or Rust? (Rust is totally sweet for server dev, and I've spun up a few Rust servers for things.)

The consultancy Nodes reports that their framework Vapor[0] that is written in Swift is "around 100 times faster" than other frameworks written in PHP, Ruby and Python, you can see his bold claim 4 minutes in here: https://vimeo.com/193549098, but of course no benchmarks have been presented.

[0] https://vapor.codes/

Re: Pushing Swift to the Server

#30

Wow. That "same language connected by an interface schema would have prevented Mars mission loss" thing is a really thin stretch.

This submission reminds me of "Satirical hacker news post"

""" The Muskonauts figured out why their shit exploded. Hackernews, literally all of whom are actual rocket scientists, wonders if unit tests could have helped. """

Also conveniently forgetting that Computer Scientists are yet to solve types physical dimensions mapping in practical programming language.

https://hackage.haskell.org/package/dimensional

Post reply on HN