How About Tomorrow?
What Does “Full Stack” Mean? w/ Taylor Otwell and Ryan Florence
This episode isn’t summarized yet
Create a free account and summarize it. In a few minutes you’ll have the key takeaways and a section-by-section summary.
Show notes
Taylor Otwell and Ryan Florence join us to talk about whether "full stack" is a term worth using in 2024, how Laravel differs from Rails, why there isn't a real JavaScript community, what Taylor would like to see from the Remix community, and whether Laravel is like Canada.
Want to carry on the conversation? Join us in Discord.
- wip: terminal
- ButcherBox: Meat Delivery Subscription
- Cloud Monitoring as a Service | Datadog
- Connect, Protect and Build Everywhere | Cloudflare
- Adam Wathan (@adamwathan) / X
- What is Amazon API Gateway? - Amazon API Gateway
- Inertia.js - The Modern Monolith
- Reason · Reason lets you write simple, fast and quality type safe code while leveraging both the JavaScript & OCaml ecosystems.
Topics:
- (00:00) - Filthy JavaScript developers
- (00:30) - What does full stack mean?
- (10:46) - How Laravel different from Rails?
- (16:17) - Is the frontend and backend team divide real?
- (18:47) - Why isn't there a JavaScript community?
- (36:32) - Are JavaScript frameworks in the best position to be the fullest stack?
- (46:18) - What about Blitz.js?
- (49:34) - What would Tayor like to see from the Remix community?
- (54:41) - Is Rails worse than building an app with Cloudflare?
- (56:38) - Is the top of funnel for web development JavaScript?
- (01:07:17) - Is Laravel like Canada?