3 ms·
I don't want to mention individual projects and services, but the two most common experiences are: 1. Documentation. A chat provider and a serverless framework
by nailer 7y ago
I don't want to mention individual projects and services, but the two most common experiences are:
1. Documentation.
A chat provider and a serverless framework where the documentation or the typescript definitions weren't kept up to date with the code. Having to check types and their REST API and 'suck it and see' to actually find out how it works. If you want contributors, your OSS project should have working demos. If you want customers, the same.
2. Unnecessary complexity. I think there's going to be a major change in the front end world in the next few years as people realise they can already achieve reactive data binding without the complexity of popular frameworks.