3 ms·
The web will not last forever. Better to build a foundation that is capable of bridging to the web if necessary than staking yet another UI layout engine atop a
by mattgreenrocks 4y ago
The web will not last forever. Better to build a foundation that is capable of bridging to the web if necessary than staking yet another UI layout engine atop a document markup syntax.
- adastra22 4y agoThat is a very interesting viewpoint. I’m not a webaholic like a lot of the JS devs out there. It’s a shit platform. But I have no illusions about its lasting power. Why do you think the web stack is going to go away?
- mattgreenrocks 4y agoIt's not that it is going away anytime soon, it is more that it is a poor choice for 'conceptual bedrock.'
- sethaurus 4y agoSure, the web will one day die — and it will certainly change a lot before that day! But even so, would you stake a current native UI toolkit to last longer, and provide more value, before that day? There are good reasons to write truly native UI. Performance is very persuasive. Longevity, perhaps less so.
- adastra22 4y agoI'll wager the Win32 gui api will outlast your choice of web stack.
- mattgreenrocks 4y agoThe conceptual foundations of something like this are extremely important. If you stake the basic ideas of the framework on the DOM, then DOM details will become implementation details which will become details that clients will depend on. And you'll have just re-written React but with even more layers. It needs to be thought about in terms of first principles, ala SICP. There are basic primitives to be defined that are the "ground," and then it is built up from there.