3 ms·
Separation of concerns is valid if you look at website as a document. If you look at website as an application components are valid approach. I don’t need a f
by ozim 2y ago
Separation of concerns is valid if you look at website as a document.
If you look at website as an application components are valid approach.
I don’t need a framework to make documents - I need framework to make web applications that is why components won so I agree.
- 8n4vidtmkvmk 2y ago> I don’t need a framework to make documents - I need framework to make web applications that is why components won so I agree. I just realized how little "content" my app has. So Nue's focus on these psuedo-Markdown documents is extra worthless. If 99% of the content is coming from the database, what would even go in these docs? It's the same at the big tech company I work at. Yes we have technical writers and UX and all that, but all the bits and bobbles of text are like 1-line long, so they go into some funky template with all the random strings and then some tooling picks them up and the translators use a custom UI to translate them. None of these folks are working directly in the codebase, nor do I think they should.