|
|
|
|
|
by Achshar
2945 days ago
|
|
I always find it curious that almost no one is talking about not using a framework to begin with. I have been writing complex UI with vanilla js for some time now, never had any issues or took longer than I expected to get a job done. |
|
After the first few web apps, one necessarily sees the repetitive elements and wants to capture that in libraries and abstractions. Routing URLs? Reuse that widget? This is just coding instinct.
I think it is possible to have a stream of projects where each new one gets its framework copied and pasted from the previous. That does not mean it's not a framework, just one without name and documentation.
Then there are projects of a certain size that you wouldn't want to do like this. Stakes too high, more than 1-2 developers. Then you can either brush up your framework and give it a name and documentation and contribute to the 'problem' of too many frameworks.
Or use something that others use and is just as suitable.