4 ms·
You are building application - I could estimate from your description alone that you're better off wrapping the DOM interactions. For websites that need intera
by the__alchemist 3y ago
You are building application - I could estimate from your description alone that you're better off wrapping the DOM interactions.
For websites that need interaction, DOM manipulation is IMO a better move due to it using a more fundamental/universal skill, light or no build process, faster execution, and explicitness.
This is a categorization, with lots of room for grey areas! I bring it up because your use case falls squarely in the category that benefits from a framework.
- danielvaughn 3y agoYeah, agreed. I was hoping I could lean into a quasi-HATEOAS approach, where the state of the editor is reflected in the state of the html output. My thinking was that if it's only in the html, then in theory it would handle very large numbers of nodes better, since you don't have to correspondingly increase the size of JS object in memory. I'm still attracted to that idea, but it's not worth it in the short term.