📝 By Aqsa – May 2025

🚀 Making the Shift: Why I Left JavaScript (for Now)

As a student developer exploring full-stack development, I started where most people do — in the world of HTML, CSS, and JavaScript. I dipped into frameworks like React, Node.js, and even played around with the MERN stack.

But the deeper I went, the more I felt like I was stitching together too many pieces — React for the frontend, Express for the backend, MongoDB for the database, and then random libraries for routing, state, auth, and more.

So, I asked myself:

“Is there a more unified, less chaotic way to build full-stack web apps?”

That's when I discovered Blazor and the broader .NET ecosystem — and everything changed.

💡 Blazor: C# Comes to the Frontend

For years, JavaScript ruled the browser. But Blazor breaks the mold by allowing us to write interactive frontend apps using C# and WebAssembly. No JavaScript. No React. Just components, pages, and events — all in C#.

At first, I thought it was too good to be true. But after experimenting with it, I found that:

I could reuse code between backend and frontend.
I didn’t need to rely on multiple third-party libraries.
I had a cleaner structure with built-in features like routing, forms, and validation.

It felt powerful. Clean. Modern. And most importantly — consistent.

🧠 What I'm Learning

Even though I haven't finished my full-stack Blazor app yet, here's what I've learned (and loved) about the experience so far:

✅ Frontend in Blazor: Writing Razor components with C# logic — no JSX, no bundlers, no DOM headaches.
✅ Backend with ASP.NET Core: Clean APIs, structured middleware, and built-in support for JWT auth.
✅ Database with SQL Server: A rock-solid relational database that pairs beautifully with .NET.
✅ Using ADO.NET: I'm diving deeper into data access with raw SQL and manual connection handling. It’s helping me understand what's really going on behind Entity Framework — and making me a stronger backend dev.

🆚 Why Not MERN?

Many of my peers are building their projects using MERN, and it’s a great stack — no doubt. But I noticed a few challenges:

Too many moving parts and third-party packages.
Constant context switching between languages.
Less built-in structure — more DIY wiring.

.NET gives me something I value more right now: a solid, opinionated foundation that supports enterprise-level apps — and my own learning process.

💬 Final Thoughts: Choosing the Stack That Chooses You Back

The beauty of web development today is that we have choices. For me, the choice to move from JavaScript to C# for full-stack development wasn’t just about curiosity — it was about finding clarity, structure, and depth.

Blazor, ASP.NET Core, SQL Server, and ADO.NET have taught me not just to build apps, but to understand them deeply.

I’m still building, still learning — but I’ve already learned this much:

You don’t have to follow the crowd to build something incredible.

📌 Stay tuned: I’ll be sharing more updates as I complete my Blazor full-stack project — Dastkari, a platform for Pakistani artisans and creators.

✍️ Blog by Aqsa

From JS to C# : Exploring Full-Stack Web Dev with Blazor and .NET