Saksham Gupta
@0xsaksham.bsky.social
🚀 Want more takes on @react.dev, @nextjs.org , and cutting through the hype?
👨💻 Follow @0xsaksham.bsky.social for:
✅ Unfiltered tech insights (no fluff).
✅ Deep dives on React, TanStack, Vite, and Next.js.
✅ Tips to build faster, simpler apps (without over engineering).
15/n
👨💻 Follow @0xsaksham.bsky.social for:
✅ Unfiltered tech insights (no fluff).
✅ Deep dives on React, TanStack, Vite, and Next.js.
✅ Tips to build faster, simpler apps (without over engineering).
15/n
March 21, 2025 at 7:20 PM
🚀 Want more takes on @react.dev, @nextjs.org , and cutting through the hype?
👨💻 Follow @0xsaksham.bsky.social for:
✅ Unfiltered tech insights (no fluff).
✅ Deep dives on React, TanStack, Vite, and Next.js.
✅ Tips to build faster, simpler apps (without over engineering).
15/n
👨💻 Follow @0xsaksham.bsky.social for:
✅ Unfiltered tech insights (no fluff).
✅ Deep dives on React, TanStack, Vite, and Next.js.
✅ Tips to build faster, simpler apps (without over engineering).
15/n
Special thanks to Kyle Gill for the blog on Nextjs v/s Tanstack
Checkout the original blog here: kylegill.com/essays/next-...
14/n
Checkout the original blog here: kylegill.com/essays/next-...
14/n
Next.js vs TanStack
See this post for inspiration. Over the past few months, I've moved as much code as possible away from Next.js . While I see why people…
kylegill.com
March 21, 2025 at 7:20 PM
Special thanks to Kyle Gill for the blog on Nextjs v/s Tanstack
Checkout the original blog here: kylegill.com/essays/next-...
14/n
Checkout the original blog here: kylegill.com/essays/next-...
14/n
If you’re happy with Next.js and it works for your team, that’s awesome!
But if you’re looking for simplicity without sacrificing performance, give TanStack + Vite a try.
It might surprise you! 😊
13/n
But if you’re looking for simplicity without sacrificing performance, give TanStack + Vite a try.
It might surprise you! 😊
13/n
Next.js vs TanStack
See this post for inspiration. Over the past few months, I've moved as much code as possible away from Next.js . While I see why people…
kylegill.com
March 21, 2025 at 7:20 PM
If you’re happy with Next.js and it works for your team, that’s awesome!
But if you’re looking for simplicity without sacrificing performance, give TanStack + Vite a try.
It might surprise you! 😊
13/n
But if you’re looking for simplicity without sacrificing performance, give TanStack + Vite a try.
It might surprise you! 😊
13/n
Final Thoughts
Next.js is great if you need hyperscale optimizations or love its ecosystem.
But for most projects, TanStack + Vite offers a cleaner, faster, and more cost-effective alternative.
I’m done with Next.js—for now. 🚀
12/n
Next.js is great if you need hyperscale optimizations or love its ecosystem.
But for most projects, TanStack + Vite offers a cleaner, faster, and more cost-effective alternative.
I’m done with Next.js—for now. 🚀
12/n
March 21, 2025 at 7:20 PM
Final Thoughts
Next.js is great if you need hyperscale optimizations or love its ecosystem.
But for most projects, TanStack + Vite offers a cleaner, faster, and more cost-effective alternative.
I’m done with Next.js—for now. 🚀
12/n
Next.js is great if you need hyperscale optimizations or love its ecosystem.
But for most projects, TanStack + Vite offers a cleaner, faster, and more cost-effective alternative.
I’m done with Next.js—for now. 🚀
12/n
Global State Management with TanStack Query
11/n
11/n
March 21, 2025 at 7:20 PM
Global State Management with TanStack Query
11/n
11/n
Example with TanStack Router
Simple, typesafe, and elegant!
10/n
Simple, typesafe, and elegant!
10/n
March 21, 2025 at 7:20 PM
Example with TanStack Router
Simple, typesafe, and elegant!
10/n
Simple, typesafe, and elegant!
10/n
Why TanStack + Vite?
1. Simplicity: Auto-complete routing with TanStack Router and validated search params via Zod by @colinhacks.com.
2. Speed: Vite is blazing fast and gets out of the way.
3. Transparency: APIs are intuitive and easy to debug without vendor lock-in.
9/n
1. Simplicity: Auto-complete routing with TanStack Router and validated search params via Zod by @colinhacks.com.
2. Speed: Vite is blazing fast and gets out of the way.
3. Transparency: APIs are intuitive and easy to debug without vendor lock-in.
9/n
March 21, 2025 at 7:20 PM
Why TanStack + Vite?
1. Simplicity: Auto-complete routing with TanStack Router and validated search params via Zod by @colinhacks.com.
2. Speed: Vite is blazing fast and gets out of the way.
3. Transparency: APIs are intuitive and easy to debug without vendor lock-in.
9/n
1. Simplicity: Auto-complete routing with TanStack Router and validated search params via Zod by @colinhacks.com.
2. Speed: Vite is blazing fast and gets out of the way.
3. Transparency: APIs are intuitive and easy to debug without vendor lock-in.
9/n
Performance Problems
Even with Turbopack, dev server compilation times were slow compared to @vite.dev.
Vite compiles in milliseconds and feels lightweight without sacrificing functionality.
8/n
Even with Turbopack, dev server compilation times were slow compared to @vite.dev.
Vite compiles in milliseconds and feels lightweight without sacrificing functionality.
8/n
March 21, 2025 at 7:20 PM
Performance Problems
Even with Turbopack, dev server compilation times were slow compared to @vite.dev.
Vite compiles in milliseconds and feels lightweight without sacrificing functionality.
8/n
Even with Turbopack, dev server compilation times were slow compared to @vite.dev.
Vite compiles in milliseconds and feels lightweight without sacrificing functionality.
8/n
SPAs Are an Afterthought
@nextjs.org heavily promotes server-side APIs over client-side rendering (CSR).
SPA support feels secondary and lacks robust documentation compared to alternatives like @tanstack.com.
7/n
@nextjs.org heavily promotes server-side APIs over client-side rendering (CSR).
SPA support feels secondary and lacks robust documentation compared to alternatives like @tanstack.com.
7/n
March 21, 2025 at 7:20 PM
SPAs Are an Afterthought
@nextjs.org heavily promotes server-side APIs over client-side rendering (CSR).
SPA support feels secondary and lacks robust documentation compared to alternatives like @tanstack.com.
7/n
@nextjs.org heavily promotes server-side APIs over client-side rendering (CSR).
SPA support feels secondary and lacks robust documentation compared to alternatives like @tanstack.com.
7/n
Debugging Issues
@nextjs.org’s heavy abstraction makes debugging a nightmare.
With 3 separate caches (Full Route Cache, Data Cache, Router Cache), tracing issues is far from straightforward.
Simpler setups like @vite.dev don’t have this problem.
6/n
@nextjs.org’s heavy abstraction makes debugging a nightmare.
With 3 separate caches (Full Route Cache, Data Cache, Router Cache), tracing issues is far from straightforward.
Simpler setups like @vite.dev don’t have this problem.
6/n
March 21, 2025 at 7:20 PM
Debugging Issues
@nextjs.org’s heavy abstraction makes debugging a nightmare.
With 3 separate caches (Full Route Cache, Data Cache, Router Cache), tracing issues is far from straightforward.
Simpler setups like @vite.dev don’t have this problem.
6/n
@nextjs.org’s heavy abstraction makes debugging a nightmare.
With 3 separate caches (Full Route Cache, Data Cache, Router Cache), tracing issues is far from straightforward.
Simpler setups like @vite.dev don’t have this problem.
6/n
March 21, 2025 at 7:20 PM
The Downsides of Next.js
1. Overkill for smaller apps: Many APIs (e.g., ISR) are unnecessary for startups or mid-sized teams.
2. Financial incentives: Many features tie you to
@vercel.com's services, making switching costly.
4/n
1. Overkill for smaller apps: Many APIs (e.g., ISR) are unnecessary for startups or mid-sized teams.
2. Financial incentives: Many features tie you to
@vercel.com's services, making switching costly.
4/n
March 21, 2025 at 7:20 PM
The Downsides of Next.js
1. Overkill for smaller apps: Many APIs (e.g., ISR) are unnecessary for startups or mid-sized teams.
2. Financial incentives: Many features tie you to
@vercel.com's services, making switching costly.
4/n
1. Overkill for smaller apps: Many APIs (e.g., ISR) are unnecessary for startups or mid-sized teams.
2. Financial incentives: Many features tie you to
@vercel.com's services, making switching costly.
4/n
3. Great for e-commerce or apps needing micro-optimizations.
3/n
3/n
March 21, 2025 at 7:20 PM
3. Great for e-commerce or apps needing micro-optimizations.
3/n
3/n
What Next.js Does Well ?
1. Easy setup: Out-of-the-box (OOTB) integrations for tools like MUI, Markdoc, and @datadoghq.com.
2. High-scale optimization: Advanced APIs like SSR, ISR, edge functions, and caching make it ideal for large-scale apps.
2/n
1. Easy setup: Out-of-the-box (OOTB) integrations for tools like MUI, Markdoc, and @datadoghq.com.
2. High-scale optimization: Advanced APIs like SSR, ISR, edge functions, and caching make it ideal for large-scale apps.
2/n
March 21, 2025 at 7:20 PM
What Next.js Does Well ?
1. Easy setup: Out-of-the-box (OOTB) integrations for tools like MUI, Markdoc, and @datadoghq.com.
2. High-scale optimization: Advanced APIs like SSR, ISR, edge functions, and caching make it ideal for large-scale apps.
2/n
1. Easy setup: Out-of-the-box (OOTB) integrations for tools like MUI, Markdoc, and @datadoghq.com.
2. High-scale optimization: Advanced APIs like SSR, ISR, edge functions, and caching make it ideal for large-scale apps.
2/n
🦀 Want to see it in action? We'll print out the command-line arguments and use them in our minigrep project to search for a string in a file. Stay tuned for more updates!
#RustLang #CommandLine #ProgrammingTutorial
#RustLang #CommandLine #ProgrammingTutorial
March 12, 2024 at 6:21 PM
🦀 Want to see it in action? We'll print out the command-line arguments and use them in our minigrep project to search for a string in a file. Stay tuned for more updates!
#RustLang #CommandLine #ProgrammingTutorial
#RustLang #CommandLine #ProgrammingTutorial
🦀 Once collected into a vector, we can access individual arguments using indexing. This helps in parsing and processing the arguments effectively.
March 12, 2024 at 6:21 PM
🦀 Once collected into a vector, we can access individual arguments using indexing. This helps in parsing and processing the arguments effectively.
🦀 Note: `std::env::args()` may panic if any argument contains invalid Unicode. For simplicity, we'll use it here, but for complex scenarios, consider `std::env::args_os()`.
March 12, 2024 at 6:21 PM
🦀 Note: `std::env::args()` may panic if any argument contains invalid Unicode. For simplicity, we'll use it here, but for complex scenarios, consider `std::env::args_os()`.
🦀 By collecting the iterator into a vector using `collect()`, we can easily access and manipulate the command-line arguments within our Rust program.
March 12, 2024 at 6:21 PM
🦀 By collecting the iterator into a vector using `collect()`, we can easily access and manipulate the command-line arguments within our Rust program.
🦀 Start by creating a new project with `cargo new minigrep`. We'll learn how to effectively handle command-line arguments in this project.
🦀 Rust provides `std::env::args()` to read command-line arguments. It returns an iterator of the arguments passed to our program.
🦀 Rust provides `std::env::args()` to read command-line arguments. It returns an iterator of the arguments passed to our program.
March 12, 2024 at 6:20 PM
🦀 Start by creating a new project with `cargo new minigrep`. We'll learn how to effectively handle command-line arguments in this project.
🦀 Rust provides `std::env::args()` to read command-line arguments. It returns an iterator of the arguments passed to our program.
🦀 Rust provides `std::env::args()` to read command-line arguments. It returns an iterator of the arguments passed to our program.