News for hackers. Stuff that matters.
Re:Swift 3.0 Release Process by stepanhruda on Saturday May 07, 2016 @05:12AM (#11648914)
I haven't seen any data. Scala has been around for a while, which means more time to spend on optimization, so it's probably faster at this point. Because of garbage collection on JVM, Swift has the potential to be more performant though.

Unless you are trying to build some really high performance shit, what really matters is developer productivity, which is abysmal for server-side Swift right now. Getting better every day though.

Source: built and deployed a service in Swift

Re:Swift 3.0 Release Process by lennelpennel on Saturday May 07, 2016 @05:27AM (#11648954)
I know you did not mean to say that scala code is non-performent. Well written jvm is highly performant and with GC algos like concurrent mark and sweep or garbage first and a good allocation of eden, tenured (etc) space you should really never have a stop the world because of GC'ing anymore.
Re:Swift 3.0 Release Process by chillacy on Saturday May 07, 2016 @04:01PM (#11651147)
While it's true you should never stop the world for CMS in a server-side program where you can control memory tuning, newgen collection is still stop-the-world, and can cause multi-millisecond pauses on ~8GB heaps.