I think this is the wrong read on the “threat”. One user going out of their way to spent time writing this post is a canary in the coal mine. Most users never give feedback, they just churn. This is the same reason your toothpaste has a phone number on the back - that one random person who cares deeply calls the number and provides invaluable feedback on the product.
It’s not about the one person, it’s about that person representing tens/hundreds/thousands of customers. This feedback is a gift to a product manager that listens.
Some states in the US have banned cell phones or other devices that can connect to cell networks. In our school district at least can connect is the key. Teachers aren’t going around testing if old iPhones have SIM cards so all iPhones are banned. (To be clear, I don’t except them to do that.)
Seems like a lot of kids would love iPods to listen to music at school like we did when I was in high school.
Thanks for checking it out. The focus of Zudoku is on making it super easy to ship beautiful API documentation. There are tons of alternatives, but we didnt feel like anything out there met our bar in terms of design and ease of use.
Zudoku is also the basis of part of our product (zuplo.com) offering so it is extremely extensible. Our managed, hosted version builds on the extensibility of Zudoku to add additional capabilities like API Key management, analytics, etc. Anyone can use these extensibility points to add their own custom capabilities.
Rate My OpenAPI uses Spectral under the hood for a lot of the checks. This is meant to be a quick (and fun) service to help people improve their API docs. Doing full linting with Spectral is complementary - and more than this tool does.
People don’t build applications on Salesforce because it’s a generic platform, they build on it because they need to integrate with the sales/crm process/data/etc.
Edit: To be clear, I’m not saying your idea isn’t good. There is tons of room for this stuff, but be careful in assuming the reason devs use Salesforce platform is because of the features. It’s usually not.
The last time I went to Woodcraft, the guy there was raving about the CNC and recommended I get one. Hard pass. Woodworking is my escape from computers. I’m sure if you do woodworking for a living a CNC is amazing, but I’ll take the slow path on this.
You don't know when this code was written or what the original purpose was. User agent detection used to be a best practice. Onedrive for business is a mountain of legacy software going from sharepoint to groove to who knows what. This bug could be buried in some library that was written 5+ years ago. Maliciously going out of your way to not support Linux sounds like a good way to have your code review rejected.
That doesn't sound right at all. It's been a number of years since I have been at MS, but any engineering team I worked on would have wanted this feedback and fixed the problem. Not supported officially doesn't mean a dev can't spend an hour on a likely simple fix to help a customer - depending on who saw this feedback there are certainly many devs at MS who would fix this without even being asked. I'm willing to bet that's happening right now and this will be resolved in a few days.
It’s not about the one person, it’s about that person representing tens/hundreds/thousands of customers. This feedback is a gift to a product manager that listens.