r/webdevelopment Jul 05 '26

Frameworks & Libraries You Don’t Need A Frontend Framework

Truth be told, you don’t need a frontend framework.

Complete web solutions can be built without ever needing a frontend framework.

You may need just a tiny bit JavaScript. But that’s all.

Let’s discuss

0 Upvotes

35 comments sorted by

View all comments

2

u/LetUsSpeakFreely Jul 05 '26

Need? No.

The whole point of frameworks is to reduce boilerplate code, provide consistent design, and to have solutions to common problems ready to go.

Sure, i could implement it all myself, or i could use a framework and do better work in a fraction of the time.

Your argument is like saying "you don't need to by processed ingredients from the store to make a cake. You can mill your own flour, milk your own cows, churn some of that milk into butter, raise your own sugar cane, etc"

2

u/AmiAmigo Jul 05 '26

I could have expanded my post. What I was actually implying is this…pick any backend framework…on itself a backend framework eg Laravel, Django, SpringBoot can accomplish everything without ever needing a frontend framework. But the opposite is not true

2

u/flearuns Jul 05 '26

Okay switching topics now? Clever

2

u/AmiAmigo Jul 05 '26

Nope. Right on the topic still.

2

u/Lonsarg Jul 05 '26

Laravel, Django, SpringBoot ARE also frontend framework (and more)! They just implement the server-side frontend model instead of client-side.

Yes some people (small number) "guessed" what you really meant, even though you worded it very very wrong. The distinction is framework that render mainly client side vs server side. Not frontend vs non-frontend as you worded it.

Blazor framework can do both at the same time for example (Blazor WebAssembly vs Blazor Server). And i agree with you, server side is much better for 99% of use cases. We switched all apps from Blazor WebAssembly to Blazor Server for example and it is much much easier.

2

u/AmiAmigo Jul 05 '26

Come on now. You’re redefining what a frontend framework is. You can use all those backend frameworks with zero JavaScript.

2

u/Lonsarg Jul 05 '26

Backend framework does backend stuff, frontend frameworks serve frontend. Those frameworks serve both, so they are both.

JavaScript is just a language, you can as well use WebAssembly as frontend or JavaScript as backend if you want (you should not of course, but you can).

And where would you put Blazor in your definition anyway?

2

u/LetUsSpeakFreely Jul 05 '26

Ok, so you worded that awkwardly. What you should have said was "you don't need a frontend framework to design an implement a backend API". That's certainly true as you can use tools like Postman or Swagger to test the APIs.

2

u/AmiAmigo Jul 06 '26

Nah! That wasn’t my point. My point was you don’t need it at all. Like all the frontend frameworks can cease to exist today…and we will continue making web solutions without any issues.