31–40 of 66 posts
Kind of an incomplete article as there is no mention of the environmental cost. Desalination is not a magic solution. Everything is a trade off. Desalination means pumping salt back into the ocean which just compounds the problem.
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
is offical Windows support planned?
Apple has no interest to provide Windows support. They support linux because it's the most used backend OS and on top of that it's Open Source. Fortunately Swift is open source so anyone can contribute and make Windows an official port. The same happened with Go.
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.
Earlier quoted context omitted.
Apple has no interest to provide Windows support. They support linux because it's the most used backend OS and on top of that it's Open Source. Fortunately Swift is open source so anyone can contribute and make Windows an official port. The same happened with Go.
Would it not work under the new Linux subsystem for Windows at least?
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
Of course bettermotherfuckingwebsite.com uses #444 on white. bestestmotherfuckingwebsite.com probably dials it up to #777 with a light sans-serif.
I'm very happy that Apple open sourced Swift. Chris and his crew are amazing and the vibrant community definitely helps/challenge them and will bring us things like: - concurrency (at least planned) - cyclone/rust memory model! - scripting - syntactic sugras Congrats!
Can you expand on the memory model? Got any links with more information?
- Memory ownership model: Adding an (opt-in) Cyclone/Rust inspired memory ownership model to Swift is highly desired by systems programmers and folks who want predictable and deterministic performance (for example, in real time audio processing code). More pertinent to the goals of Swift 4, this feature is important because it fundamentally shapes the ABI. It informs code generation for “inout", how low-level “addressors” work in the ABI, impacts the Swift runtime, and will have a significant impact on the type system and name mangling.
is offical Windows support planned?