Twitter | Search | |
Thomas Visser
3,140
Tweets
385
Following
773
Followers
Tweets
Thomas Visser Aug 20
Replying to @Lojanda
Werkt echt lekker, gefeliciteerd met de launch!
Reply Retweet Like
Thomas Visser Aug 19
I moved to a new house! Please invalidate your caches accordingly.
Reply Retweet Like
Thomas Visser Aug 19
Replying to @AndyyHope
IIRC it’a because they want to keep the option of building a native Swift AttributedString open. Like we have String and NSString.
Reply Retweet Like
Thomas Visser Aug 10
Replying to @chriseidhof
Supercool. Wij doen ook zoiets, maar dan met heel veel Observables enzo. Dat voelt plotseling vrij complex.
Reply Retweet Like
Thomas Visser Aug 8
Replying to @thomvis
Feel free to reach out with any questions you might have! DMs are open.
Reply Retweet Like
Thomas Visser Aug 8
Replying to @thomvis
Having worked on both our iOS & Android codebases, I can say that I love working with the Android codebase. In many ways it's a better version of the iOS code. (Figures, since it's a newer codebase, but still.) Animation performance remains a challenge though.
Reply Retweet Like
Thomas Visser Aug 8
We're looking for an experienced Android engineer at . We build shopping apps with a big focus on UX. We're using Kotlin, Rx, MVVM, Dagger, Realm and more. Come work & grow with us!
Reply Retweet Like
Thomas Visser Aug 3
Replying to @steipete
Just checked and we indeed also have some missing line info when we build fully from source (with BC enabled). Using binary distribution there would be no info at all so that might be a different issue.
Reply Retweet Like
Thomas Visser Aug 3
Replying to @steipete
We stopped using binary distribution of our (internal) framework (for faster builds) b/c crash reports were missing info. No amount of redownloading dSYMs from iTC could fix it. I blamed our distribution process, but maybe it’s Bitcode and we should just disable that and move on.
Reply Retweet Like
Thomas Visser Aug 2
Did some more digging. There is private API that can tell you how deep the “hiddenness stack” is, unfortunately no public way. And UIStackView is way way way more complex than I thought.
Reply Retweet Like
Thomas Visser Aug 1
I use no nibs at all, have a lot of stack views in code and have never encountered the issue. Not sure if that proves anything 🙃
Reply Retweet Like
Thomas Visser Aug 1
Replying to @kastiglione
Thanks! So around the introduction of Swift sounds about right.
Reply Retweet Like
Thomas Visser Jul 31
Replying to @rob_rix
questions like that keep me up at night
Reply Retweet Like
Thomas Visser Jul 31
Replying to @tapbot_paul
Have you considered removing animations (from layers) after layoutIfNeeded was called in an animation block? This cancels the default (sometimes unwanted) animations and allows you to add your own instead
Reply Retweet Like
Thomas Visser Jul 31
Replying to @Javi @SmileyKeith
Could you put the dequeuing inside a performWithoutAnimation closure, as a work-around?
Reply Retweet Like
Thomas Visser Jul 23
Replying to @heathborders
This can be turned off by a willing administrator:
Reply Retweet Like
Thomas Visser Jul 23
Not sure, printing anything in lldb is quite unreliable in my experience.
Reply Retweet Like
Thomas Visser Jul 18
Replying to @vasarhelyia
Would love to chat about the iOS dev position at Highstreet in Utrecht (The Netherlands) if you’re interested. Best of luck in any case!
Reply Retweet Like
Thomas Visser Jul 12
Replying to @DnDBeyond
Created with my gf for our first ever game of D&D
Reply Retweet Like
Thomas Visser Jul 3
Replying to @thomvis
Does anybody have an idea when the ability to see a breakpoint’s locations was added to Xcode?
Reply Retweet Like