Looking back on Swift 3 and ahead to Swift 4

Post by superswordfish » Sat, Jul 30, 2016, 1:00 PM UTC

legulere wrote: post #41

superswordfish wrote: post #37

Earlier quoted context omitted.

Have you seriously never seen mailman before? You must've taken a wrong turn getting here. Of course bettermotherfuckingwebsite.com uses #444 on white. bestestmotherfuckingwebsite.com probably dials it up to #777 with a light sans-serif.

> Have you seriously never seen mailman before? Sure I have, and every time I'm annoyed by the archive site layout. > You must've taken a wrong turn getting here. No need to get personal, take a step back cool down and don't take things so serious. > Of course bettermotherfuckingwebsite.com uses #444 on white. Yeah it's also a bit too bright for my taste, but the general point still holds.

Post by smackfu » Sat, Jul 30, 2016, 1:16 PM UTC

legulere wrote: post #27

Why does mailing list archival software not contain basic css? Long lines make it hard to read the text. You don't even need much css: http://bettermotherfuckingwebsite.com

Post by superswordfish » Sat, Jul 30, 2016, 1:20 PM UTC

zoul wrote: post #45

superswordfish wrote: post #42

Earlier quoted context omitted.

Fair enough, I saw it as an attack on no-frills developer-oriented content in favor of some notion of beauty. Mailman pages, like most GNU HTML, are simple and excellent. They're accessible, resize predictably, readable, and they fill the window. They're light and download quickly. They have high information density. It's sort of baffling how narrowing the content, reducing contrast and increasing line height are an…

If not anything else, it’s pain to read on mobile. That could be easily fixed without compromising any of the good parts.

Post by pjmlp » Sat, Jul 30, 2016, 2:45 PM UTC

jernfrost wrote: post #34

Awesome things in store for Swift. With Rust like memory model as alternative and async/await I think it will massively broaden the appeal of Swift. I can start to see Swift taking over as the main mainstream language in the future. Java and C# has just accumulated too much cruft, they will be the new C++ languages. You can do anything but you have to accept a lot of complexity and awkward syntax to do that.

Post by dschiptsov » Sat, Jul 30, 2016, 2:57 PM UTC

bsaul wrote: post #28

dschiptsov wrote: post #7

Perhaps, one should borrow message-passing as a standard language idiom, actors and pattern matching on receive from Erlang, the way Akka did, instead of copying hat async/await ugly hacks. Message passing as a core concept of a language is fundamental and necessary (given that interlop with ObjC is important), and having that and macros gives related control structures for free.

Message passing unfortunately means everything is copied rather than pointed at. Which, in the case of a smartphone is always the beginning of performance or memory related problems. I think rust approach of having strong guarantees over memory ownage, and thus being able to share memory in a safe way, is a better direction for swift.