Profile avatar
jovidecroock.com
🇧🇪 | he/him | Software Engineer @Shopify | @preactjs.com core maintainer| passionate about DX & web perf
487 posts 1,018 followers 203 following
Regular Contributor
Active Commenter

This is one of the biggest releases we ever did!

Back when I was finding my feet in tech everybody was buzzing about building positive change. Somewhere along the way, something changed. Fortunately for us though, tech is not the first industry forced to defend itself against dubious practices. What might we learn if we were to look elsewhere?

I wrote about tracking contexts in Preact signals as it still often feels like a confusing topic for people. Are you seeing a lot of peek in your signals? You might want to read this!

Let me also take this opportunity with Preact being a hot-topic now that I write about Preact topics on my blog! If you want to know more about the new diffing algorithm, you can look at the source code and read a few of my articles!

> GraphQL Fragments, tragically misunderstood Could not agree more with that

This, we need more kindness around these ‘tribes’. All of us working on these tools put a lot of time and love in it, all of us have our reasons to prefer working with x or y. Let’s be accepting of that!

🍋2️⃣👀

Signals now support new `watched` and `unwatched` options. You can consider watched a lazy subscription, when the signal is first accessed it will trigger. When the last subscription is removed, unwatched will trigger.

Interested in Signals? Enjoy learning by reading code? Check out github.com/jkup/learn-s...

I am working in something *very* wild for Preact, which I believe will be a complete game changer. Actually right now I'm on vacation BUT when I get back I will continue working on this *very* wild thing. 6 year old idea but the last 2 years of Preact features make it infinitely better.

Well, that Remix announcement was exciting... Back to shipping stuff

If you are going to completely ignore the issue template… please tell us why. It enables us to improve and in the long run it helps us help you.

Introducing LiveStore (beta) LiveStore is a next-generation state management framework based on reactive SQLite and built-in sync engine. livestore.dev

Reposting for my NA signals fans

I think at this point I am holding my own little release week 😅 I've been really busy the past 5 months and having a week off now feels like all of the idea's are just overflowing

If you find an OSS issue that calls your attention, go for it. You don't need to ask permission to start working or have it assigned to you. If someone else sends a PR before you, that's great. You can use your knowledge of the issue to help review the PR, add tests, and validate the approach.