maxdesiatov

7 ms·

1.
Emscripten Target Support for Swift(forums.swift.org)
2 points by maxdesiatov 7mo ago|0 comments
2.
Swift SDKs for WebAssembly now available on swift.org(forums.swift.org)
6 points by maxdesiatov 1y ago|0 comments
3.
Structured concurrency in Swift: continuations, tasks, and cancellation(desiatov.com)
3 points by maxdesiatov 6y ago|0 comments
4.
Yet another macOS privacy protections bypass(lapcatsoftware.com)
320 points by maxdesiatov 6y ago|90 comments
5.
First stable release of SwiftWasm 5.3 is now available(forums.swift.org)
3 points by maxdesiatov 6y ago|0 comments
6.
Interactive Swift Playground Built with WebAssembly(swiftwasm-pad.netlify.app)
4 points by maxdesiatov 6y ago|0 comments
7.
The State of Swift for WebAssembly in 2020(desiatov.com)
2 points by maxdesiatov 6y ago|0 comments
8.
Open-source implementation of Apple's Combine framework(github.com)
1 points by maxdesiatov 7y ago|0 comments
9.
by maxdesiatov 7y ago
Why not?
10.
Show HN: Tokamak – React-like framework for native UI written in pure Swift(github.com)
8 points by maxdesiatov 8y ago|0 comments
11.
Swift and React Native (and Similar Libraries/Frameworks) Survey
3 points by maxdesiatov 8y ago|1 comments
12.
by maxdesiatov 8y ago
Sorry, I'm not sure I understand this point. Why would I need a different license for this from scratch implementation? What if I want Apache 2.0 as well? Also, I'm convinced that many many people do have interest in this. Many pe
13.
by maxdesiatov 8y ago
but what about reimplementing a compiler from scratch without reusing any of Apple's code? It wouldn't fall under a definition of Derivative Work under terms of Apache 2.0 then
14.
by maxdesiatov 8y ago
And also, "it protects Swift" in their context always means "it protects Apple's Swift" unfortunately
15.
by maxdesiatov 8y ago
Exactly this, thank you for summarizing this so well! I've tried to clarify this exact point at Swift Forums, but I haven't seen even a clarifying answer from anyone in the core team on this point. Everyone says "it protects
16.
by maxdesiatov 8y ago
Including from suits from Apple itself for using concepts of Swift elsewhere in projects that were developed from scratch, not forked from Apple's projects, right?
17.
by maxdesiatov 8y ago
From what we see, software patents have caused more harm than good, but would be great if there were enough concrete public examples listed somewhere that prove otherwise.
18.
by maxdesiatov 8y ago
ok, does it mean that if you implement only parts of the patent (say only a single feature) there's no infringement because then it doesn't "fit the language of the claims"? Also, "using Swift" isn't in th
19.
by maxdesiatov 8y ago
Could you please provide an example? From what specifically have any patents protected users of an open source product? I know plenty of examples when patents were used to harm the users, the most notorious one being Oracle and Java. But I
20.
by maxdesiatov 8y ago
Could you please elaborate on this? Is there any direct confirmation of this? There wasn't any single answer from anyone affiliated with the Swift core team on this specific point. Or from any lawyer for that matter.
21.
by maxdesiatov 8y ago
The biggest question here is whether this means they lose the patents when they sue something that's not covered by Derivative Works as defined in Apache 2.0? Looks like an implementation of a compiler not from Apple (that is, not a fo
22.
Apple is patenting Swift features(forums.swift.org)
580 points by maxdesiatov 8y ago|208 comments
23.
Unbreakable reference cycles in Swift no one is talking about(desiatov.com)
1 points by maxdesiatov 8y ago|0 comments
24.
by maxdesiatov 8y ago
The main reason for that is lack of hygienic macros in Swift. Currently you can use code generation tools like Sourcery and SwiftGen, but I expect 1st-class meta-programming support to come after Swift 5.0 release. After ABI stability I ima
25.
by maxdesiatov 8y ago
Except that in Objective-C it's a runtime feature, which is by definition slower. Swift's Codable implementation is generated by the compiler or is hand-written with an obvious benefit of a stronger type system.
26.
by maxdesiatov 8y ago
I appreciate such detailed feedback, thank you! Parsing of workbook.xml is implemented in the library itself in `parseWorksheetPaths` function I mentioned it briefly in the article, but decided to omit it as main focus was on Codable protoc
27.
Parsing Excel Spreadsheets with Swift's Codable Protocols(desiatov.com)
103 points by maxdesiatov 8y ago|30 comments
28.
Coroutines and “yield” expressions: foundation for async/await in Swift(desiatov.com)
1 points by maxdesiatov 8y ago|0 comments
29.
What are generators and why Swift needs them?(desiatov.com)
2 points by maxdesiatov 8y ago|0 comments
30.
Event loops, building smooth UIs and handling high server load(desiatov.com)
2 points by maxdesiatov 8y ago|0 comments

More ›