callin.cc
husband, tinkerer, đ and đ owner, and also sometimes a web dev.
257 posts
61 followers
192 following
Regular Contributor
Active Commenter
comment in response to
post
I wonder if itâs a PS5 thing, reading several other reporting the same thing on Reddit. Might wait a few patch releases before committing.
comment in response to
post
Have just spent 15 mins so far, but the sprinting is awful? Not sure I can get past that.
comment in response to
post
don't read the comments :(
comment in response to
post
www.youtube.com/watch?v=0IIo...
comment in response to
post
then don't have the liberal rogan being a conspiracy-based reaction navigated by your brotherâs loser friends. oversimplifying your opponentsâ views to their dumbest possible form and arguing against that is exactly how we ended up here
comment in response to
post
âdangerously use serverâ
comment in response to
post
if updating the key doesn't work, i would append a cache-busting query string to the url as well.
comment in response to
post
Donald Knuth would be proud :)
comment in response to
post
I recently had to use the vanilla queryClient, and really liked the query options api, until i spent time trying to figure out why the select prop didnât work :'(
comment in response to
post
Thought that observer logic could be part of useQueryClient somehow, so you have something like:
const data = use(useQueryClient().query(âŠ))
but maybe it creates more complexity than itâs worth just to consolidate the apis.
comment in response to
post
Haven't really thought this through, but is there a potential future where react-query simply is:
```
const data = use(queryClient.query(...));
```
?
comment in response to
post
Are you intentionally missing the point?
comment in response to
post
What you are suggesting is deploying workarounds that may or may not work depending on the feature, which increases complexity of maintenance and QA. And even if you choose to go down this path, you canât even easily test old versions of Safari due to its version being tied to the OS.
comment in response to
post
If you have as requirement that ~98% of users need to have updated to a version supporting :has before you can use it - it doesnât matter since version adoption of Safari lags way behind Chrome due to being tied to OS upgrades.
comment in response to
post
Whatâs something about web app development you learned at bsky you wish you knew while working on react full-time?
comment in response to
post
Nyamko�
comment in response to
post
I feel like the dataloader pattern is way too unexplored outside of graphql and would work great in the client to avoid breaking encapsulation. Same goes in your server example which works for reading files, while more realistically you want to avoid N network calls to the db.
comment in response to
post
lol ok
comment in response to
post
Is React ecosystem somehow worse than the JS ecosystem at large?
comment in response to
post
7 years ago Apple had to fight rumours about macOS slowly being replaced by iOS due to iOS getting more advanced and a perceived lack of investment in macOS, to the point they had to address this in a keynote. And people *still* didn't believe them. Feels like where React is today with RSC vs SPA.
comment in response to
post
It really feels like a UI library that has been through and survived 2-3 CSS paradigm shifts.
comment in response to
post
itâs me. hi. iâm the weird person who likes to tweak bundler configs itâs me.
comment in response to
post
I feel like you are a few iterations away from writing a React version of Gödel, Escher, Bach.
comment in response to
post
While amazing, the one thing that killed Threads for me is that I really donât want all of my Instagram and/or Facebook friends to automatically see my post. In some ways this is an anti-feature.
comment in response to
post
1990 hÀr - har vagt minne att jag hört nÄgot om det
comment in response to
post
same - I'm looking around for reactions like a junkie and when I'm not finding anything I feel like nature is healing
comment in response to
post
depends a bit on the technology chosen for storage in the client. for the simplest storage mechanism - localStorage - it's about 10MB, but there are other solutions. but now you know just about as much as i do about this area :) localfirstweb.dev developer.mozilla.org/en-US/docs/W...
comment in response to
post
generally itâs syncing all application state to local storage on first visit, and then sync back to the web server on a db level upon changes. iâm only familiar with js frameworks like electricSQL, but I believe it should be agnostic enough to handle python servers as well.
comment in response to
post
i havenât really checked out agentic frameworks, but would the local-first web app paradigm fit this?
comment in response to
post
hört att tonÄringar har börjat ÄterupptÀcka cd-skivor ganska nyligen ocksÄ!
comment in response to
post
you wouldn't dare
comment in response to
post
i think they are on to you
comment in response to
post
something like this?
comment in response to
post
I sincerely hope thatâs not an extremist view.
comment in response to
post
why can't this just be the default behavior?
comment in response to
post
@lukyvj.bsky.social⏠hi! đ is this anything you can help out with in your role as devrel engineer?
comment in response to
post
what about node v0.12 users????
comment in response to
post
assumed so :) thanks again!
comment in response to
post
omg i just searched for ref đ thanks! i sort of expected to find a single page about the ref property. maybe consider increasing the number of hits even on small search queries, if algolia allows for that?