New blog post 👀
Practical Auto-Vectorization
How to make your single-threaded loops run multiple times faster, or how I improved Swift's Base64 encoding performance to 16 GB/s.
https://t.co/L370GAp6LR
@lemire Great article as always.
I've also been working on a IP-related library: https://t.co/IDQcCvJDBU
I've managed to achieve similar speeds although on older harder, see the link for details.
SIMD specifically, I didn't manage to make it run faster than the simpler branchy code.
No affiliation, but this one's a banger. I've read it 2 times, I'll probably keep reading it once every few years just to refresh my memory.
Explains the history and the current state but doesn't go too much into the mathematical details (which you might or might not like).
Vapor (finally!) has a new merch store where you can buy t-shirts, stickers, hoodies and more! All proceeds go towards funding the development of Vapor! Check out the blog post https://t.co/rH9KZTxU3u or visit the store at https://t.co/Zq1byy0vUk
Are you using GitHub Actions for building @SwiftLang SwiftPM projects?
See how you can slash your CI times by orders of magnitude in my latest article:
https://t.co/Urg80E2E5S
@jeremyphoward Does black text on white background look good enough with/without the brightness extention? I had heard it looks a bit bad with the nano texture display.
Our WebSocket library is now also available without using the Hummingbird framework, for client development like a Discord bot, or an Android/iOS app.
It's fully structured concurrency based and Autobahn compliant. Huge thanks to @o_aberration's efforts!
https://t.co/5yXbx8wm6J
Unpopular opinion:
Swift 6's data race safety stuff are mostly nice and great.
The problem majority of people have is to get it working with the UI frameworks which are filled with Obj-C legacy (classes and inheritence).
In Server Side, Structured Concurrency is pretty neat.
New library 👀
https://t.co/P9Q0HpxprU
A middle ground between raw code and macros:
Writing boilerplate case-by-case code using Mustache templates for enums.
Swift isn't just for building client apps: there's a whole server ecosystem out there too. This session explores how Swift powers mission-critical services across Apple and beyond, and is full of useful packages and tips to help you too: https://t.co/2IgRX3Vgnr
If you’re already using Swift on Server or want to know what the hype is about make sure to checkout this years “Explore the Swift on Server ecosystem”#WWDC24 session.
We’ll explore popular packages and talk about how it powers many Apple Cloud services.
https://t.co/3pXDuW5r7Q
If you’re already using Swift on Server or want to know what the hype is about make sure to checkout this years “Explore the Swift on Server ecosystem”#WWDC24 session.
We’ll explore popular packages and talk about how it powers many Apple Cloud services.
https://t.co/3pXDuW5r7Q
@twostraws Nice article :)
There is some inaccurate info in the article about `ExistentialAny` and `InternalImportsByDefault` being enabled by default in Swift 6.
I don't blame you considering that's what the proposals say 😅, so i've also opened up this PR: https://t.co/DLi5MDq7Od
A client of mine is looking for an experienced Swift developer to join their remote backend team! The team is spread around the world. Salary expectations are 65-80K USD.
Please get in touch with me to learn more.
@jaleel_akbashev@migueldeicaza@_neonsunset@elmomertens Yeah, flagship Swift Server packages like Apple's deafult to structs and only use classes when necessary. inheritance is also basically non-existant.
Regardless, non-copyable types are still better for raw perf, since they guarantee no ARC and also no implicit-copy.
Just launched part 1 of the structured concurrency guide for Swift! This series is designed to cover the needs for iOS and backend devs alike!
https://t.co/GnS2Nc5r8v
Next week's post will cover Sendable, shared state, actor isolation and global actor.