github.com/Munawwar | codepasta.com
At Carriyo, Dubai, UAE
I've been sitting on a simpler approach FW even: github.com/Munawwar/Pep... . It does SSR + hydration + has stores all within 2kb. Hydration is so dead simple, traverse dom and attach event listeners. Down sides - no components, dom diff based
I've been sitting on a simpler approach FW even: github.com/Munawwar/Pep... . It does SSR + hydration + has stores all within 2kb. Hydration is so dead simple, traverse dom and attach event listeners. Down sides - no components, dom diff based
1. So hydration is going to be a userland concern?
2. How do you get type checking? IIUC say typescript-lit-html-plugin gives autocomplete but not type checking with tsc. Also now it needs to support framework components.
1. So hydration is going to be a userland concern?
2. How do you get type checking? IIUC say typescript-lit-html-plugin gives autocomplete but not type checking with tsc. Also now it needs to support framework components.
The one that could have complimented this is the ESX proposal.
The one that could have complimented this is the ESX proposal.
- you carry the weight of features you don't use - complexity, architecture
- FW internal bugs are you're problem yet you can't easily fix
- you need to keep up with major upgrades else you're left with a FW you don't know enough about to maintain. And this is on avg every 2 years
- you carry the weight of features you don't use - complexity, architecture
- FW internal bugs are you're problem yet you can't easily fix
- you need to keep up with major upgrades else you're left with a FW you don't know enough about to maintain. And this is on avg every 2 years
I also liked @rschristian.dev 's reply last time I said that: "But what if I want to shoot lightning from my hammer?"
😂 Man, that's exactly how devs think these days!
I also liked @rschristian.dev 's reply last time I said that: "But what if I want to shoot lightning from my hammer?"
😂 Man, that's exactly how devs think these days!