3 ms·
yeah, I could see that. web3.js is a super bloated library and will be added more frequently unless a team does a more optimal version from scratch https://gi
by yieldcrv 4y ago
yeah, I could see that.
web3.js is a super bloated library and will be added more frequently unless a team does a more optimal version from scratch
https://github.com/ChainSafe/web3.js/issues/1178 https://github.com/ChainSafe/web3.js/issues/1178
- iainmerrick 4y agoThe second-last comment on that issue is pretty clear: The issue with the lib is its non-treeshakeable nature. It should be rewritten using ES6 modules. That doesn't seem so hard, unless I'm missing something. Certainly shouldn't need a full rewrite from scratch. My point is, it's not just about bloat and having too many features (which are very hard problems to fix); it's often low-hanging fruit that isn't being picked.
- pavlov 4y agoLuckily it's very easy to avoid these "web3 dapps" (sigh). And if you don't, an extra megabyte of JavaScript junk seems like a minor problem compared to the usual crypto user experience of losing all your money and/or becoming a cultish bore.
- yieldcrv 4y agofortunately there are many other crypto user experiences that don't require cultish fealty to a project or token ready contract data from the nearest node is a pretty benign and common aspect of what web3 inclusion in a site does. just accessing variables and constants in a cloud data store that can be read for free.