| > I'm not in the US either but I'm sure someone will know how to make it happen, even if it goes to charity or something. (no crypto though) I'm not up for a charity thing - if we're betting I want to be able to win as well as lose - but if there's a way to do it then I'm down. > I guess the second bet's criteria would depend on both the recommended practice for moving components today and the recommended practice in the future (which we don't know yet so it'd have to be done in good faith). Right, yeah, happy to just say we look at it in good faith and reach a conclusion. > Currently, web components are designed to be portable so they can easily be ported between projects by copy-pasting a single hunk of code. > Whereas react components can be copy-pasted, but (as far as standard practice is concerned) require build systems and their dependencies (both of which rot over time) before they can be considered functional. I don't think that's a huge difference; copy-pasting your dependency declarations and your implementation is not conceptually any harder than copy-pasting just your implementation. If the accepted dependency format changes, or your component needs custom build steps, then that might be a harder piece of porting (but I wouldn't consider a simple mechanical change like changing dependency notation from JSON to XML to be a significant burden). |