Native all the way, until you need text
A seasoned macOS/iOS developer reflects on the challenges of implementing rich text and Markdown in native Apple frameworks, despite years of experience and deep platform knowledge. After extensive efforts using SwiftUI, AppKit, and TextKit 2, the developer found that none provided reliable, performant text handling for modern chat applications. Ultimately, web-based solutions like Electron delivered superior results, raising questions about the viability of native tooling for complex text interfaces.
- ▪The developer spent significant time trying to implement a Markdown-enabled chat in SwiftUI but encountered fundamental limitations in text selection and scrolling behavior.
- ▪Switching to NSTextView, AppKit, and even raw TextKit 2 failed to deliver stable performance or seamless integration with modern SwiftUI workflows.
- ▪WebKit provided a workable solution, but an Electron prototype outperformed all native attempts in text handling, rendering, and feature completeness.
- ▪The experience revealed that Apple’s native SDKs struggle with rich text use cases common in contemporary applications like chat and long-form content.
- ▪The developer concludes that for complex text interfaces, web-based frameworks are now more capable than Apple’s native tools, despite the expectation to use native technologies.
2 outlets in our directory ran this story, first to last over 2 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
- ▪ Native all the way, until you need text — Reddit
Hacker News (Front Page) files mainly under programming. We currently carry 742 of its stories. Top-voted stories on Hacker News.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Hacker News (Front Page) |
| Canonical URL | https://justsitandgrin.im/posts/native-all-the-way-until-you-need-text/ |
| Publication time | Sun, 17 May 2026 11:49:46 +0000 |
| Retrieval time | 2026-05-17T12:32:13.085Z |
| Last seen | 2026-05-17T12:32:13.085Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | ZpCgnvNqbmZt · 2 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
I have been a native macOS / iOS developer for almost twenty years, and I want to say something about the usual “Oh, it is Node / Electron again… what a shame…” reaction. Recently, I tried to implement a simple chat with Markdown support in a pure Swift / SwiftUI app. And honestly, it is almost funny how immature all these “native” things still are when you step outside simple screens. Yes, you can achieve reasonable performance in SwiftUI. You can even convince yourself that jumpy scrolling is fine, and that a few lags here & there are acceptable. But then you want to select a whole Markdown document built from SwiftUI primitives, and you just cannot. By design. So, being smart & experienced, you move to NSTextView. It even supports TextKit 2 now. Great.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Hacker News (Front Page).
Discussion
0 commentsMore from Hacker News (Front Page)
