Michał Miszczyszyn
@typeofweb.com
I build software | Startupper / Blogger / Activist / Published Author / Speaker / He, him
Welcome to the family!
November 25, 2024 at 12:28 PM
Welcome to the family!
MacBook Pro M4 Space Black:
- 14‑core CPU, 20‑core GPU, 16‑core Neural Engine
- 48GB unified memory
- 1TB SSD storage
- standard display
- 14‑core CPU, 20‑core GPU, 16‑core Neural Engine
- 48GB unified memory
- 1TB SSD storage
- standard display
November 19, 2024 at 8:58 AM
MacBook Pro M4 Space Black:
- 14‑core CPU, 20‑core GPU, 16‑core Neural Engine
- 48GB unified memory
- 1TB SSD storage
- standard display
- 14‑core CPU, 20‑core GPU, 16‑core Neural Engine
- 48GB unified memory
- 1TB SSD storage
- standard display
US: AI revolution
Meanwhile EU:
Meanwhile EU:
November 16, 2024 at 3:01 PM
US: AI revolution
Meanwhile EU:
Meanwhile EU:
How I feel trying experimental dynamicIO in Next.js canary
November 13, 2024 at 11:25 PM
How I feel trying experimental dynamicIO in Next.js canary
Good morning. My favourite spot in SF, best coffee in town, and I’m ready to write more TypeScript 🤓
November 13, 2024 at 3:56 PM
Good morning. My favourite spot in SF, best coffee in town, and I’m ready to write more TypeScript 🤓
What are we thinking? Will it blend? 🤔
November 11, 2024 at 9:25 PM
What are we thinking? Will it blend? 🤔
This is what happens when humans code instead of AI
😡😠😡😠
😡😠😡😠
November 8, 2024 at 8:36 PM
This is what happens when humans code instead of AI
😡😠😡😠
😡😠😡😠
Found it! The @splinetool.bsky.social component doesn't trigger Suspense for rendering, but it provides a way to add rendering fallback.
So, I ended up adding the same fallback twice:
So, I ended up adding the same fallback twice:
November 6, 2024 at 12:39 AM
Found it! The @splinetool.bsky.social component doesn't trigger Suspense for rendering, but it provides a way to add rendering fallback.
So, I ended up adding the same fallback twice:
So, I ended up adding the same fallback twice:
I find using async DOM APIs without promise support a bit awkward. I always have to wrap them with `new Promise(…)`.
Recently, I found `Promise.withResolvers()` simpler and more readable to use. What do you think?
Recently, I found `Promise.withResolvers()` simpler and more readable to use. What do you think?
November 4, 2024 at 8:16 PM
I find using async DOM APIs without promise support a bit awkward. I always have to wrap them with `new Promise(…)`.
Recently, I found `Promise.withResolvers()` simpler and more readable to use. What do you think?
Recently, I found `Promise.withResolvers()` simpler and more readable to use. What do you think?