Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Server APIs Project

swift.org

Post reply on HN
Print view View original

11–20 of 181 posts

Re: Server APIs Project

#11

Post by sacheendra »

ruddct wrote: post #9

Great. Great great great. A thousand times great. We've been slowly converting our iOS projects over to Swift over the past year and the results have been tremendous (a ~40% drop in LOC from ObjC, among many other benefits). Really the only language-level feature that feels missing for server development is first-class support for asynchronous/concurrent operations, but that's coming. Swift is truly a 'best of most w…

I think most languages thatare popular today are 'best of most worlds' for their users. For example, Scala has all the features you specified and has an even larger ecosystem of libraries for the server side.

I am still happy that this has been done as I know having a common API to program against does ease development and creates a great ecosystem as evidenced by node.JS.

Re: Server APIs Project

#12

Post by amelius »

Nice, but I prefer a language which runs both on client and server, because that means I can share code, and e.g. I can do prerendering on the server and stuff like that.

Re: Server APIs Project

#13

Post by K0nserv »

amelius wrote: post #12

Nice, but I prefer a language which runs both on client and server, because that means I can share code, and e.g. I can do prerendering on the server and stuff like that.

But Swift does run on both the client and the server. Not when the client is web, but when the client is an iOS or macOS app.

Re: Server APIs Project

#14

Post by [deleted] »

amelius wrote: post #12

Nice, but I prefer a language which runs both on client and server, because that means I can share code, and e.g. I can do prerendering on the server and stuff like that.

[deleted]

Re: Server APIs Project

#16

Post by [deleted] »

ruddct wrote: post #9

Great. Great great great. A thousand times great. We've been slowly converting our iOS projects over to Swift over the past year and the results have been tremendous (a ~40% drop in LOC from ObjC, among many other benefits). Really the only language-level feature that feels missing for server development is first-class support for asynchronous/concurrent operations, but that's coming. Swift is truly a 'best of most w…

[deleted]

Re: Server APIs Project

#18

Post by daenney »

amelius wrote: post #12

Nice, but I prefer a language which runs both on client and server, because that means I can share code, and e.g. I can do prerendering on the server and stuff like that.

That depends a bit on what you define as prerendering. Facebook, Google and many others render client views server side (or as much as possible). See Spotify's recently open sourced HubFramework for example for how they do that with iOS. Having multiple languages doesn't preclude you from doing clever things like that and having a single language doesn't necessarily allow you to do it either.

Re: Server APIs Project

#19

Post by steveklabnik »

squiguy7 wrote: post #3

I have been following Rust's push into server-side development and can tell it is still green. There is a great foundation with the hyper library but quite a bit of fragmentation with frameworks and the async side of things. It will be interesting to see where swift goes with all this. I know Rust has a lot of traction now with cross-platform support and language features, but I think swift is poised to offer a much…

The async side is all coalescing around Tokio and its various sub-projects.

I too am excited to see where this goes; Swift is a great language.

Re: Server APIs Project

#20

Post by amelius »

daenney wrote: post #18
amelius wrote: post #12

Nice, but I prefer a language which runs both on client and server, because that means I can share code, and e.g. I can do prerendering on the server and stuff like that.

That depends a bit on what you define as prerendering. Facebook, Google and many others render client views server side (or as much as possible). See Spotify's recently open sourced HubFramework for example for how they do that with iOS. Having multiple languages doesn't preclude you from doing clever things like that and having a single language doesn't necessarily allow you to do it either.

Yes, but a single language makes it a lot easier.
Post reply on HN