Going Back To Next
Theo - t3․gg・2 minutes read
Cody shares his journey back to JavaScript and preferences for development tools, highlighting the benefits and drawbacks of coding with Go, Temple, and HTM X. He recommends using React for front-end tasks and Go for back-end performance to achieve optimal results.
Insights
- Cody, a prominent figure in the tech community, showcases his journey back to JavaScript, emphasizing the importance of developer and user experience while exploring various programming languages like Go and HTM X.
- TRPC's advancements in V10 and tools like Next.js offer significant benefits for project management and development efficiency, highlighting the value of seamless transitions between front-end and back-end code for creators.
Get key ideas from YouTube videos. It’s free
Recent questions
What video did Cody release after "Goodbye JavaScript"?
"Hello JavaScript, Oh How I've Missed You"
Related videos
Summary
00:00
"Cody's Tech Journey: Hello JavaScript"
- Cody released a video titled "Hello JavaScript, Oh How I've Missed You" after his previous video "Goodbye JavaScript" received attention.
- Cody is praised for his understanding of the Day Zero community and his contributions to the T3 stack.
- Cody made changes to his content based on conversations, including adjustments to his video format.
- Cody involves his Twitch chat to address issues with video content that doesn't fit his and Cody's faces.
- Cody discusses his journey back to JavaScript after trying Go and HTM X, citing developer and user experience as key factors.
- Cody appreciates Cody's public exploration of his tech journey and his honesty in sharing the process.
- Cody highlights the benefits and drawbacks of coding with Go, Temple, and HTM X, expressing a preference for Next.js.
- Cody praises Go's simplicity and performance but notes its verbosity and limitations in string interpolation.
- Cody appreciates Go's error handling compared to Node.js but finds it verbose at times.
- Cody values the speed and efficiency of tools like the T3 stack, emphasizing the importance of building fast without sacrificing correctness.
12:13
TRPC's V10 Advancement Enhances Project Management
- TRPC's significant advancement with V10 allowed for command-clicking from the front end to the back end, enhancing project management for creators.
- A hook for infinite queries was created for a page query API for managing images, utilizing paginated images and infinite queries.
- The front-end component runs on the client side, enabling easy navigation to the backend code through command-clicking.
- The server file contains the server code for DB queries and returns, showcasing the seamless transition from front-end to backend code.
- Open API's TypeScript generator allows for generating types from an Open API V3 spec, enhancing safety and efficiency.
- The Open API React Query binding by Martin Pocket enables a type-safe API client for Open API backends, ensuring type errors and definitions.
- TRPC offers a deeper integration compared to Open API, providing clear endpoints like `API.image.getPageImages` for easy access and understanding.
- JSX simplifies development by allowing HTML-like syntax within JS files, enhancing type safety and ease of use.
- Issues with Temple's live reload feature causing browser freezing highlight the importance of efficient hot module reloading in modern web tools.
- HTM X's default behavior causing button state issues during redirects emphasizes the need for user-friendly experiences and efficient bug fixes in web development tools.
25:11
"Go vs Typescript: Backend Efficiency and Productivity"
- In Go, to keep a file private, it should not be exported, allowing all content in the file to access it.
- Go is preferred for building performant backends due to its strict typing and concurrency model, especially for running multiple tasks simultaneously.
- Node workers are considered cumbersome compared to Go's channel-based approach for handling work distribution.
- Go is recommended for larger teams working on complete REST APIs or microservices without front-end concerns.
- Context shifting between different projects is easier in Go due to its consistency, making it ideal for backend-focused developers.
- Typescript is favored for minimizing context shifting between front-end and back-end tasks, enhancing productivity.
- React's design goal is to enable developers to work seamlessly on both front-end and back-end without extensive context shifting.
- HTM X is critiqued for increasing context shifting between front-end and back-end tasks, leading to a preference for Typescript.
- Next.js is praised for its ease of use and productivity in setting up features like Kanban boards quickly compared to Go or HTM X.
- Using React for front-end and API requests for back-end tasks is suggested for smoother development, reducing context shifting challenges.
37:40
Optimal Tech Stack for Performance and Experience
- To prioritize back-end performance, Go is recommended, while for front-end user experience, React in TypeScript or other client-side technologies are suggested.
- If both back-end performance and front-end user experience are crucial, a combination of Go for the back end and React for the front end is advised.
- For a focus solely on user and developer experience, React with Next.js is recommended for all aspects.
- If back-end performance is the main concern, Go with HTMX is a suitable choice.
- Node.js with frameworks like Next.js is suggested for those prioritizing server performance and not overly concerned with back-end performance.
- The speaker emphasizes the importance of considering the balance between back-end performance and front-end user experience, suggesting React for the front end and Go for the back end for optimal results.
