Hector Matos 🇵🇷🇪🇨

16.5K posts

Hector Matos 🇵🇷🇪🇨 banner
Hector Matos 🇵🇷🇪🇨

Hector Matos 🇵🇷🇪🇨

@krakendev

I write bugs in iOS apps you’ve probably used. ADHDer who loves FFXIV/OW/D&D/Legend of Zelda 💕 https://t.co/zFIBmJ6sRk

Austin, TX Katılım Mayıs 2009
2.9K Takip Edilen3.8K Takipçiler
Hector Matos 🇵🇷🇪🇨 retweetledi
Nay.Tesseract
Nay.Tesseract@brittnaynay3·
🎉 Pc Giveaway 🎉 💜😈 Custom Solo Leveling Hyte Y70 Themed PC 💻✨ How to Enter: 1. 🔁 Retweet & ❤️ Like this post 2. 👣 Follow Me @hytebrand and @Palit_Global 3. 💬 Drop a comment 🌍 Worldwide giveaway 🎯 Bonus Entries: 💬 Comment on my other socials more comments = more chances! 🔗 Links in bio & pinned below 🗓️ Winner announced in 7 days 🍀 Good luck, Shadow lovers 😈💜
Nay.Tesseract tweet media
English
32.4K
23.7K
29.2K
1.5M
Hector Matos 🇵🇷🇪🇨
@BKAngryKing @SebJVidal @SEDIDEL While he did provide a working example, his list of what Seb did wrong is incorrect and Seb outlined why each piece of feedback is incorrect. The feedback provided should’ve correctly addressed WHY Seb’s example is not working as intended but it didn’t.
English
0
0
1
226
Angurī Wappā
Angurī Wappā@furiouswhopper·
@SebJVidal @SEDIDEL Dude he provided a working example of what you failed to do and you still claim he's wrong? wtf is this mentality...?
English
2
0
4
147
Seb Vidal
Seb Vidal@SebJVidal·
It's hard not to add fuel to the "is SwiftUI production-ready" fire when this is the state of the "best way to build an app" 6 years after the framework was released... 🙃 ~30 lines of (admittedly sloppy) but simple code, unusable on iOS 26. Oh! And it works just fine on 18 🫠
English
32
9
280
67K
Jacob Bartlett
Jacob Bartlett@jacobtechtavern·
Advanced SwiftUI tip for iOS devs: I love using enums to implement my design systems. You can get progressive disclosure, intelligent defaults, and full customisation within your system. (composition shills are welcome to spew vitriol below)
Jacob Bartlett tweet mediaJacob Bartlett tweet mediaJacob Bartlett tweet media
English
3
3
73
6.1K
Hector Matos 🇵🇷🇪🇨 retweetledi
Feristal J
Feristal J@FeristalJ·
R.i.P Mare thank you for everything
Feristal J tweet mediaFeristal J tweet media
English
137
542
4.1K
1.1M
Nick Williams
Nick Williams@TheNickster27·
@drakanous Honestly I never did an escape room type of game before, it was a unique experience I called my friends about it and immediately came over to help out...one got jump scared by the calyx locker
English
1
0
22
4.2K
Drak (is authorized to hunt)
Drak (is authorized to hunt)@drakanous·
So I've heard a lot of people say they DIDN'T like the "escape room" from the 7.3 MSQ... but I kinda enjoyed not having "press A simulator" for once. I actually took notes. Am I alone or are other enjoyers just laying low?
English
388
166
2.4K
110.8K
Hector Matos 🇵🇷🇪🇨
@krzyzanowskim I can’t give away all of my secrets but yes she definitely said that. As for if it’s true - let’s just say I am wise beyond my years
English
0
0
1
100
Hector Matos 🇵🇷🇪🇨
I’ve just been informed by my daughter that I’m so fat and old that I caused the Big Bang
English
1
0
2
232
Hector Matos 🇵🇷🇪🇨
Told my wife she has “bodacious bazongas” today and my daughter overheard it. She retched and said “please don’t ever say that again” and ran away. Kids these days just don’t understand romance
English
0
0
5
179
Jacob Bartlett
Jacob Bartlett@jacobtechtavern·
How does Swift 6.2 Approachable Concurrency behave? Swift was originally introduced with a clear vision of “progressive disclosure”, where it was easy to pick up, and more complex language features would slowly become clear as you needed more advanced use cases. In early 2025, the Swift team released a vision document in Swift Evolution that admitted the original implementation of Swift 6 strict concurrency checking to guarantee memory safety was a little heavy-handed, and went against progressive disclosure (anyone maintaining pre-concurrency legacy project with 3,000+ noisy Sendable-related warnings can attest to this). The vision introduced a path to progressive disclosure of concurrency: 1. Single-threaded sequential code, without parallelism or data race issues. 2. Async code without data-race safety errors, allowing basic suspension. 3. Introducing parallelism to achieve high performance, using the compiler to protect against data races. The Swift 6 language mode enables this progressive disclosure with new features that introduce this “approachable concurrency” configuration. The “Default Actor Isolation” mode allows you to tie a whole app to the MainActor, creating a new single-threaded default mode for Swift Concurrency. In modular apps, this might can be applied across UI modules, with the rest of your libraries working in parallel. There is also an “Approachable Concurrency” language mode which affects the way tasks are scheduled on executors. It slightly simplifies the way actor context is inherited: an async function call called from a @MainActor function will inherit the same main actor context. Swift 6.2 also introduces a new keyword, @concurrent. This is an explicit way to offload work to a background thread. When you want a function to run on a background thread, you can explicitly mark it with this attribute. Interestingly, for URLSession network calls, these run on a background thread by default, so they won’t block while suspended, even with full main actor and approachable concurrency modes enabled. You can also use this attribute when declaring a Task. The net effect of these changes is to make Swift Concurrency more predictable, and simpler to adopt incrementally. Data race safety in high-performance parallel code can be achieved, but bread-and-butter feature work shouldn’t be encumbered with hard-to-parse data isolation warnings. In short, when you are rolling a multi-module app, you can’t go wrong making your UI modules concurrent. With new projects, it’s a great idea to start off with the strictest possible concurrency and isolation settings, then moving away when required. When both approachable concurrency and default actor isolation are enabled, Michael Long’s research showed that your code can always be expected to run on the main thread, except in 3 cases: - The @concurrent attribute - Any actor other than the main actor (they have their own serial executor, remember!) - A detached task Take my new Swift Concurrency course here 🧵🚀 blog.jacobstechtavern.com/p/swift-concur…
Jacob Bartlett tweet mediaJacob Bartlett tweet mediaJacob Bartlett tweet media
English
2
6
42
3K
BluBao
BluBao@BluBao_art·
Keep pushing keep cooking work even harder RAAAA!! 🔥🔥🔥🔥🔥🔥
English
1
1
12
942
Hector Matos 🇵🇷🇪🇨
@xgigglypuff I can’t believe I let him make it to second base. We were scheduled for third base tomorrow but I’ve since canceled our appointment I don’t know what to do now
English
0
0
2
102
giggly ♡
giggly ♡@xgigglypuff·
@krakendev There are four people in this thread dating our boyfriend, Hector 😩
English
1
0
19
1.5K
giggly ♡
giggly ♡@xgigglypuff·
I don’t want to post in one of those “Are We Dating the Same Guy” facebook groups because I don’t want to make it weird, but I was hoping I could reach out to you guys to investigate. I’ve been seeing this guy for awhile, and I’m suspicious that he’s seeing other people. He makes great money at a tech company, which is a huge perk, but he’s told me different company names every time I ask? And he mentions different coworkers. Is this not a red flag? It seems like he can’t even remember. If he were actually at work when he cancels plans with me, wouldn’t he be able to keep his story straight? His name is Soham Parekh, if any of you all are also seeing him, please let me know.
English
122
89
4.5K
253.4K