The author has a point here, collaboration without a driver will lead to a culture of talking instead of doing. To be a driver of a change you need agency. Great example with the PR. If I create a PR at another team, how will they react? "Get off my lawn" or "actually this is not something we had in mind but thanks for the PR, we are putting it behind a feature-flag and will try it out and measure the outcome".
Yeah, right? They really have a great website. Even better, the sourcecode is on github with 200+ open PRs, 10.000+ closed PRs and 133 authors in this repo over the last months.
Please bro, please, fix our bugs bro, just this one bug bro, last one I swear, you and I will make big money, you are the best bro, I love you bro.
-- big tech companies
I'm considering a new reMarkable, but the lack of an official sdk for the cloud API is a major concern.
The community has built amazing tools for remarkable device, but their work is constantly being broken by software updates. This isn't a sustainable situation. For a company that charges for a cloud service, providing a stable, official API should be a priority. It would not only support the community's innovation but also provide a reliable foundation that developers and users can trust for the long term.
As long as a stable, official API isn't provided, I won't be buying a new device from them.