Wait, what did they do to Slack? How did this go unnoticed? I have 21 teams in it, how does it not consume a gig of RAM for each team anymore?

`mds_stores` consumed 7 gigs in the meantime, `accountsd` is at 3 gigs. Native apps rule, I guess? ¯\_(ツ)_/¯

One more reason to stop using Slack (as if consuming more memory than the rest of the active apps on your system combined wasn't enough): turns out you can't delete your account from a workspace ¯\_(ツ)_/¯


Well, that was quick, just one week later here's XMLCoder 0.11 with a bugfix for CDATA decoding, support for Combine's TopLevelEncoder protocol, and also a new rootAttributes argument for the encode function. The latter was implemented by Luís Portela Afonso 👏


New day, new release. This one is CoreXLSX 0.10, a new version of the Excel spreadsheet format parser written in Swift. As usual, thanks to everyone who made it possible, seeing feedback and contributions is always inspiring 🤩


Yes, it's ugly, but on the bright side:

* Escape key!
* No more accidental taps on Touch Bar (I wish I could buy my next MacBook Pro without the Touch Bar)
* No more accidental touches on the trackpad when palms rest on the keyboard
* Inverted T-shape arrows 👏

Show thread

New version of XMLCoder is out, now supporting Linux with Swift 5.0.1 or later! Also, you can now decode enums with associated values (see screenshot). Thanks for the hard work to @drewag, James Bean and Ben Wetherfield 👏 github.com/MaxDesiatov/XMLCode

Sometimes I feel a bit of frustration with the package management situation in : CocoaPods, Carthage, SwiftPM and Xcode integration, no binary packages etc. Then I spend a bit of time with the Python ecosystem and realize that Swift is doing pretty well after all 😄🐍🦅

Working with SwiftSyntax on a lower level, I start discovering things I didn't know were possible or made sense at all. Case in point: top-level computed properties 🤯

(Not that I plan to use this in my code, but I always expected something like this would be a compiler error)

has a dependency on an unreleased Swift 5.1 feature, check out this `@state` property attribute. This does look like the recently returned for revision Property Delegates proposal. Can safely bet it's gonna be accepted in some shape by fall 2019 github.com/apple/swift-evoluti

Remember when people were saying Microsoft would ruin ? I don't think that's exactly what's happening, especially with the new Sponsors initiative. I'm on the waitlist and I hope it would allow my open source projects to become sustainable 🙏 github.com/sponsors

Super interesting approach to type checking in dhall-lang.org: you can request an explanation for any errors that will print a short related reference and full reasoning for the error 😯

If I were able to change only one thing about right now, I'd allow most statements (if not all of them) to be used as expressions. Would help so much with pattern matching nested values 🤓

I'm super excited to publish the first release of Tokamak: React-like framework for native UI written in pure Swift 🛠⚛️📲

I've worked on this nights and weekends of the last 7 months (with a ton of help from Matvii Hodovaniuk 🙏) 👨🏻‍💻

Check it out here 👇

Getting closer to the initial release of my UI framework written in pure Swift based on React Hooks API. New milestone today: renderer for macOS 🎉 (there's already iOS renderer). You could potentially write apps for both UIKit and AppKit with a lot shared UI code (w/o Marzipan!)

I wish people creating new libraries for Promises/Futures in Swift spent as much energy and effort on research of alternative approaches (algebraic effects, coroutines, actors) and proposals/implementations for Swift Evolution. Why keep reinventing the wheel? ¯\_(ツ)_/¯

Clang and LLVM (and Swift too as it's based on those projects) wouldn’t exist if C and C++ were “protected by patents from patent trolls”, because then LLVM and Clang would infringe on those patents. Nothing bad happened to languages without patents, they’re doing perfectly fine. Java and Oracle on the other hand… 🙈

I was happy with my 2018 MacBook Pro, I like TouchBar, I like how the keyboard feels. I also cleaned the keyboard as much as I could to avoid any dust destroying it, which  said shouldn't happen with 2018 model. None helped. 😱 Now I have to use this: github.com/aahung/Unshaky

TIL: never underestimate performance testing in XCTest: just found a significant performance regression in XMLCoder PR. 🤔 Many thanks to Vincent Esche for providing the tests! 👏 github.com/MaxDesiatov/XMLCode

Oh dear... Am I the only one who feels that CMake is not "the right way" to do cross-platform build systems? Don't we deserve something better? LLVM projects Y U NO use better build infrastructure? Why is there even a need to inject files "to suppress noisy CMake warnings"? 😣

Show older

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!