HN user

krzyzanowskim

592 karma

I do stuff at https://swift.best

Posts33
Comments55
View on HN
www.fiercehealthcare.com 4mo ago

The AI in minutes, solves patient care problem that stumped doctors for months

krzyzanowskim
1pts1
commanderai.app 6mo ago

Show HN: Commander AI – Mac UI for Claude Code

krzyzanowskim
4pts3
notepadexe.com 9mo ago

Show HN: Notepad.exe – macOS editor for Swift and Python (now Linux runtime)

krzyzanowskim
41pts50
saagarjha.com 2y ago

Swift Concurrency Waits for No One

krzyzanowskim
3pts0
www.judo.app 4y ago

Server-Driven UI – Everything Old Is New Again

krzyzanowskim
3pts1
twitter.com 4y ago

We have 60 apps on the AppStore. They go through the same rules that the 1.7M do

krzyzanowskim
1pts0
dominickm.com 4y ago

Windows 11 – A Dev’s Perspective – It's great

krzyzanowskim
3pts0
www.judo.app 4y ago

What Is Server-Driven UI?

krzyzanowskim
55pts59
www.judo.app 4y ago

Show HN: Judo - Build Native App Experiences with No Code

krzyzanowskim
103pts64
www.psychologytoday.com 5y ago

No doubt that S. Jobs met criteria for a Narcissistic Personality Disorder 2012

krzyzanowskim
1pts0
panic.com 5y ago

We’ll stop selling our Code Editor app for iOS soon

krzyzanowskim
353pts436
twitter.com 5y ago

Apple’s tech interview scope for junior position

krzyzanowskim
105pts120
www.nytimes.com 5y ago

Everything wrong with Google's first decade of elitist hiring practices (2013)

krzyzanowskim
5pts1
www.corbinstreehouse.com 5y ago

The Sad State of Logging Bugs for Apple (2019)

krzyzanowskim
9pts1
twitter.com 6y ago

Apple Photos app don't accept photo downloaded from iPhone because it's not JPEG

krzyzanowskim
17pts3
bartstechblog.blogspot.com 6y ago

Dependency Heck – Swift

krzyzanowskim
2pts1
twitter.com 6y ago

10 years ago, that animation worked flawlessly

krzyzanowskim
3pts0
www.cnet.com 6y ago

Google pays $11M to settle with job seekers who alleged age discrimination

krzyzanowskim
2pts0
blog.krzyzanowskim.com 8y ago

Funding (my) OpenSource work

krzyzanowskim
4pts0
blog.goodstuff.im 9y ago

Why you should move away from AgileBits

krzyzanowskim
6pts1
twitter.com 9y ago

Objective-C Dinosaur. Some of us are dinosaurs shirt

krzyzanowskim
1pts0
blog.krzyzanowskim.com 9y ago

Framed faces. The real world status board

krzyzanowskim
1pts0
twitter.com 10y ago

Status of App Store review process

krzyzanowskim
1pts0
blog.krzyzanowskim.com 10y ago

Fast pattern search in Swift since 1974

krzyzanowskim
5pts0
blog.krzyzanowskim.com 10y ago

How to change iCloud password in 57 steps

krzyzanowskim
4pts1
blog.krzyzanowskim.com 11y ago

Photos – you do it wrong Apple. In 2015

krzyzanowskim
26pts13
blog.krzyzanowskim.com 11y ago

Show HN: Natalie – Storyboard Code Generator for Swift

krzyzanowskim
3pts0
blog.krzyzanowskim.com 11y ago

Swift: Raw{Not}Representable enum

krzyzanowskim
1pts0
blog.krzyzanowskim.com 11y ago

Swift: Madness of Generic Integer

krzyzanowskim
148pts75
medium.com 11y ago

Show HN: Privacy – PGP Messenger

krzyzanowskim
10pts5
OpenAI Presence 8 hours ago

Marketing departament went ahead and drop "battle-tested product" nobody ever battle tested.

I don't know where's the improvements, give it has all the limitations, now scaled to rich text. That's not the direction that this component should get. It need radical new API that is not much compatible with SwiftUI API

totally. the there's a lot complexity that adds up to the overall performance issues. and TextKit 2 IS pretty bad at things. especially public API is pretty bad - that result in my case need to workaround things that I should've not. I agree with the general sentiment et all. I also still believe there is a place without bringing the whole browser machine to render text, and have text under control - but without relying on the "TextKit" level. That's the next thing I'm researching right now.

SwiftUI, (but not specifically "SwiftUI", more of paradigm) is not the right tool to incremental changes of large portion of data, and SwiftUI specifically is very bad at it and offer no good API to make incremental changes more optimal. That's one of the reason behind why Apple to this day did not ship usable SwiftUI text view component.

annoyingly enough, the API has some sort of background layout support. I don't think it works well, though. I tried to use it, but it did not improve the "main thread" operations sigificantly to have an impact of fast scrolling scenario - I suspect it may not work actually

as long as we deal with estimated values, it is inescapable. the best we can do is tune the estimate calculations and tweak heuristics. that's my understanding of the problem, but I'd love to hear from other experience

I personally would not attempt to build an alternative to UITextView on TextKit (1 or 2)

sure. If only UITextView/NSTextView did not have bugs impossible to workaround otherwise. TextKit 2 support in UITextView/NSTextView was really bad. improved over time. and still remain buggy. The UITextView focus limits the use of TextKit 2 architecture significantly.