It would be hard to understate how large of a feat of engineering this was. PostGraphile is such a powerful tool and it's great to see such a great foundation for the future in v5
Kudos to @benjie.dev, Jem, and all who contributed to Postgraphile
This is the biggest gap in Next.js I’ve stumbled on (or at least the biggest gap in the docs)
Immediate impulse purchase.
Josh's animations are SO COOL and I can't wait to learn his tricks!
Josh builds the highest quality educational materials I've seen in the world of web software development
If his last 2 courses are any indication, I'll be referencing this for years. I highly recommend checking it out
C++ is much easier post-ChatGPT.
Was grumbling that current project forced my hand into building a portion in C++, and now I'm breezing through building it
Dependency management is also much better than it was in ~2016, but it is still very rough. make's pip look good
Sounds good. Excited for the outcome of animation land :)
For example, how and when does the reducer/updaterFn get called?
How should one handle concurrent pending updates?
I'd love to see a post on React's useOptimistic from @joshwcomeau.com 😁
The React docs and existing resources out there are too high level. They don't actually explain how it actually works in detail - they just show an example of how it's used.
In my experimentation, it seems sneakily nuanced!
unstable_cache is of limited usefulness right now for my app without better support for granular cache revalidation
Diving into Next.js and it feels like the cacheing primitives are designed more for semi-static sites than for dynamic ones
e.g. it'd be huge have cache tags be dynamic. Then I can revalidate a single cache entry, not just the entire cache
really hope they're working on this
Delightful little post on what happens when you don't understand the *why* behind copy-pasting a solution from the internet. Even more important in the age of vibe coding / LLMs
smoores.dev/post/no_such...
🎉 Introducing my upcoming third course, Whimsical Animations!
This course will teach you how to build top-tier animations and interactions using a variety of techniques. ✨
You can join the waitlist on the course’s brand-new site, which is the most ridiculous thing I’ve built in quite some time:
I wonder how much economic output has been eviscerated debugging CORS issues
2 - Show the infra-as-code alongside the traditional UX and have them live update each other. Look to
zoo.dev's interface as inspiration
This would be such a helpful bridge between the gap of the UI and the code
2 things I'd love to see from new cloud providers like
Railway, Fly.io,
1 - an LLM to chat with that has the context of the state of your whole account. "Why am I seeing X?" "It could be because this setting is set over here"
uh, I think I found a bug in Chrome rendering today??
Great candidate for Yes Yes No
Anytime I am helping someone with CSS and they seem to have the wrong mindset in how they approach writing it, I tell them to watch this video by @miriam.codes
As far as I'm concerned it should be required viewing for anyone who is learning CSS.
youtu.be/aHUtMbJw8iA?...
rust is basically a really nice version of javascript
Someone should do a regular TypeScript “Packages we Love” inspired by @oxide.computer’s “Crates we Love”.
It’s a delightful format, and I imagine everyone listening would learn something
oxide-and-friends.transistor.fm/episodes/cra...
Finishing up ESLint’s financials for 2024 and…it’s not pretty. ESLint ran at a nearly $60,000 deficit. We managed due to our prioritizing building up our reserves for several years prior in case of a rainy day. We can use your help closing the gap.
eslint.org/donate
It's kinda wild how slow the F street car in SF is. Pretty sure it's significantly slower than a bike. Would be curious to see if ridership numbers justify its existence
Time and time again, I keep coming back to @joshwcomeau.com's CSS and React courses to refresh my memory on something. They ay very well be the best resources on the internet on those topics
www.joyforjs.com
Manually managing focus state in a web app is not a fun time. Would not recommend it
(also couldn’t find a better way for supporting keyboard nav through elements in a canvas??)
Kinda wild that we don’t have an HTTP status code for partial success other than 206, which seems focused on the range request
I wonder what would break if the GraphQL community just commandeered a 2xx number and started using it. We’ve still got plenty of numbers, right? 😅
I know that ship has already sailed, but it’s a tiny shame that the term “query” is used in GraphQL requests to refer to the whole document and to the query operations. Could’ve calledthe request the “document” or maybe “queryDocument” to better disambiguate. Naming is hard
I don’t know when aliases became a thing but I just learned about them and they’re awesome
