I'm currently developing an application where the backend is in .NET, which I'm comfortable with. I'm deciding between using Blazor or SvelteKit for the frontend. This project is for a client, so SEO isn't a priority. I'm looking for opinions on which technology would be more practical and future-proof. I've laid out some pros and cons for each:
**Blazor Pros:**
- Full C# stack for frontend and backend, eliminating context switching.
- Smooth integration with the .NET ecosystem.
- Server-side Blazor avoids large JavaScript bundle concerns.
**Blazor Cons:**
- Smaller community compared to mainstream JS frameworks.
- Limited UI library ecosystem relative to JS frameworks.
- Blazor WASM has performance and size overhead.
**SvelteKit Pros:**
- Modern, lightweight JavaScript framework, often easier for devs to learn than React, Angular, or Vue.
- Access to a large ecosystem of UI libraries and tools.
- Excellent performance and developer experience.
**SvelteKit Cons:**
- Requires switching from C# to JS/TS for the frontend.
- Despite growing quickly, has a smaller community than React or Vue.
- Less seamless integration with .NET for APIs and authentication.
Given all this, I would love to hear your experiences and recommendations: should I stick with Blazor for a unified C# experience, or go with SvelteKit for its modern development features?
6 Answers
Ever thought about needing features not included in Blazor? If you plan to expand or scale, I'd recommend going with a common JS framework API. Just look at job trends; React, Vue, and Angular are the top dogs right now. If you don’t see a need to expand, then Blazor would be perfectly fine for you!
If your team values a smooth workflow and you're already strong in C#, Blazor Server is a great option. It allows for shared models and easy auth integration, making it fantastic for internal tools. However, if you're leaning towards more feature-rich UI options or lightweight bundles, SvelteKit with TypeScript offers speed and a robust ecosystem. Just make sure to treat your APIs as versioned contracts so everything stays organized!
Trust me, steer clear of Blazor. In my experience, the hot reload feature is a nightmare as your codebase grows. You’ll encounter unexpected issues that'll drive you up the wall. SvelteKit is the way to go! Plus, it can help you generate APIs easily with tools like Openapi-ts. Definitely gives a smoother development experience.
I personally really enjoy using Blazor. For internal apps, it’s been super straightforward and works just fine. Definitely gives a nice feeling of control and familiarity!
If you're building a business-focused SaaS dashboard, Blazor WASM paired with Mudblazor could be a good match. But for consumer-facing applications where you want a sleek, smooth experience, SvelteKit is usually better since it's more lightweight and easier to work with.
From my experience, developing web apps feels swift with Blazor. We've relied on it for various internal components and find it effective. It just clicks well for business apps.
Related Questions
Cloudflare Origin SSL Certificate Setup Guide
How To Effectively Monetize A Site With Ads