The author reflects on their current tech stack choices for a course web application, opting to use Go, Temple, HTMX, and AlpineJS instead of their usual stack that includes React and Next.js. They discuss the benefits and drawbacks of each technology, such as Go's efficiency, Temple's immaturity in developer tooling, and the complexities of using AlpineJS and HTMX. They also touch on third-party integrations like SQL C, Clarke for authentication, and Stripe for payments, alongside their plans for future changes, including evaluating Alpine Ajax as an alternative to HTMX and considering different payment and email solutions.
•24m watch time
7 Comments
Sort: