3 ms·
Your argument reads like a fallacy (over-generalization): "UI/UX modifications were carried out on a single project with terrible results, so all UI/UX changes
by Funes- 6y ago
Your argument reads like a fallacy (over-generalization): "UI/UX modifications were carried out on a single project with terrible results, so all UI/UX changes must be useless on any other project".
Look at it this way (taking a decentralized network as an example): either one of I2P's two most used implementations (Java & C++) would greatly benefit from adding an informative configuration wizard to set speed limits, enabling or disabling features, help set up UPnP or manually forward ports, etcetera. Such a small addition would make wonders for adoption. UX improvements cannot be ruled out, especially not that hastily.
- Mediterraneo10 6y agoIronically, setting up UPnP or manually forwarding ports is hard in some countries today because the ISP insists you use their broadband router, and it runs a locked-down firmware where those settings are not available to end users (unless customers upgrade to their more expensive business plan). So, another example where it is the ecosystem that is biased against general-purpose computing – or at least general-purpose networking – and UI tweaks can’t change that.