sh03.dev
🇮🇹🤌 Software Dev. Primarily: Typescript, React, PostgreSQL.
464 posts
104 followers
206 following
Getting Started
Active Commenter
comment in response to
post
Weird indeed. This is Chrome on Android.
comment in response to
post
I meant the top most blog post. The one that is always above the fold.
comment in response to
post
The last post doesn't have the title transition like other posts. You might wanna look into that. Otherwise looks cool 😎
comment in response to
post
... lean
comment in response to
post
comment in response to
post
What's one thing you found surprising about SEO?
comment in response to
post
In other words the way I read the principle is "astonishing the user in gratuitous ways when there's a clear consensus that yields the same results can be bad and should be avoided".
comment in response to
post
I think you are reading too much into it. I think that a back button on the bottom right of the screen is clearly astonishing behavior that is not good. That's what it usually refers to. Of course astonishing the user in good ways (e.g. the first iPhone not having a physical keyboard) can be good.
comment in response to
post
justusesignals.net
comment in response to
post
Instead of being this aggressive and gate-keeping fellow engineers why don't you spend this time sharing little nuggets of wisdom about accessibility (I'm assuming you know a lot on the topic) so that everyone can improve and learn?
comment in response to
post
Eh. It was possible to have something similar already via js-joda. Not sure it's that groundbreaking.
comment in response to
post
I'm done with click baity articles on AI.
comment in response to
post
If you meet this archetype just run.
comment in response to
post
I'm sure that's coming from the same people that published:
"Any skilled developer can write perfect JavaScript. Typescript is just for people who can't even write good code."
and produced:
"Any skilled developer can write perfect code. Testing is just for people who can't."
comment in response to
post
Absolutely. What worries me about things like AWS is DDoS Attack stories where the final bill is in the hundreds or even thousands of dollars. I don't think I'd be able to handle bills like those for a pet project.
comment in response to
post
It's good internet igiene to immediately unsubscribe from emails you don't care about. If they don't have an unsubscribe link at the bottom then Mark as spam and report.
comment in response to
post
What about when you SaaS is used moderately (e.g. 1k monthly active users). I'm sure those bills will spike. As always it's a tradeoff. Low billing for low usage, astronomically high billing for high usage.
comment in response to
post
Yeah bluesky is full of bots that like posts based on keywords. Had the same experience with keywords like SEO, AI, PWA (???).
comment in response to
post
Anything related to PWAs
comment in response to
post
comment in response to
post
Tbf the divide is real. Client side code is run on a different hardware than server side code (as you pointed out also in a recent article).
comment in response to
post
Starts a fun maze game to pass the time 👾
comment in response to
post
Do you have examples of all of this? As a Tailwind-aholic I can't imagine going back to CSS.
comment in response to
post
That's the only part I understood. What are the 3 dots?
comment in response to
post
I see
comment in response to
post
OP's image seems to show a popover which seems worse since you have to hover over an option to discover it's the one you have used last time.
comment in response to
post
Or show a "you used this last time" below the method
comment in response to
post
Fuck yeah! That's awesome 😎
comment in response to
post
I'd fetch the whole recipe at the top 😏
comment in response to
post
If you have ensureQueryData in your loaders then IIRC link preloading (which again IIRC is enabled by default on hover in TTS) will run the loader for future links by default.
comment in response to
post
tanstack.com/router/lates...
comment in response to
post
Tanstack Start (and probably other frameworks) usually support link prefetching for that use case as well which is as fast and efficient as it gets.
comment in response to
post
Sharing this here also
comment in response to
post
Bluesky needs code blocks
comment in response to
post
The first number after the second hyphen (-) is the version number of the UUID so it's fixed for every UUID of that version.
comment in response to
post
Just one last thing: my position is not a "this way sucks, mine is better". Our JS world needs people that wake up one day and say "what if we could do this better" and actually try. So I hope your vision succeeds and it turns out I was wrong. It's a pretty beautiful vision, that's for sure. GL
comment in response to
post
Have been shaped by years of PHP, the awe of the first AJAX apps, and then PWAs and it shows.
Still in awe that tools like Google Docs and Linear exist.
comment in response to
post
Amen to that
comment in response to
post
I'm not ready to concede this point but I'm also about to have dinner. I'll just say this: IMHO client side navigation after first load (Tanstack Start) has much better tools to avoid stalling, flickering and jumpiness (prefetch queries, prefetch route, cached data, etc).
👋
comment in response to
post
But then again I'm a "fetch at the top when possible" kind of guy so I wouldn't recommend that pattern anyway.
comment in response to
post
Sorry, I forgot about the part where each post fetches its own data. Yeah that wouldn't work well with loaders (although it's technically possible to implement it with the same performance with ensureQueryData).
comment in response to
post
True but I don't think about it as another layer. Also most of the when I want this single roundtrip it's for a specific reason (e.g. SEO) so optimizing specific pages is an option.
Maybe you could enforce this with tests + useSuspenseQuery + a suspense boundary that throws an error or something.