Looking for some feedback from #webdev folks.. I'm experimenting with migrating a #nextjs project to Astro. On paper, the site is a great candidate - content-focused (blog, articles) looking for lighter client experience and better dev experience. https://astro.build/
I have a CMS wired up and have started migrating a couple React components. What gotchas are hiding deeper in this project? Where are the common pitfalls with Astro?
Hey folks, we're kicking off a new pledge drive to accelerate the development of Bridgetown, an "alt #Ruby" web framework which starts off in the #Jamstack and vanilla-first, #HTML-first, #WebComponents-friendly development, but provides the ability to scale up to dynamic fullstack applications & publications.
Version 2.0 is underway with modernization, performance, and of course new features all on the table!
Consider sponsoring today to ensure 2.0 absolutely rocks. 🤘
When I was promoting #Jamstackyears ago one of the points that I emphasized most was that it's great to avoid technology- and vendor lock-in.
But then the vendors came.
I guess that was inevitable. If all you offer is a "nicer" way of building and distributing static sites then companies who can do it cheaper will catch up. It's most likely just the same infra underneath. You need to offer something that makes people prefer your platform over others.
The entire point and the beauty of static website is that they are self contained and portable. By adding more and more APIs for sure makes it less portable and fragile to some extend. Simplicity is not simple anymore.
😶🌫️ @zachleat on the future of #jamstack
📊 @ChenxinLi2 on bad graphing practices
🩺 Taylor Otwell announces #Laravel Pulse
⏳ @maxim on long term refactors
📚 Spencer Baugh makes the case for libraries over services
🎙 hosted by @jerod