4 ms·
Popular app takes VC money and starts charging users for previously-free features once the pressure is on to earn returns. Users – who have been freeloading for
by paxys 4y ago
Popular app takes VC money and starts charging users for previously-free features once the pressure is on to earn returns. Users – who have been freeloading for years – can easily move to something else (or write their own version), but would rather just moan about it online.
This same scenario has played out 10000x with the exact same outcome, yet people keep expecting something different from the next one.
Wtf even is a "local collection runner"?
- devmor 4y agoIts just a script that runs a collection of requests in a row, from your machine. Something every single request tool can do. A very basic feature that requires absolutely no resources from Postman's servers.
- paxys 4y agoSo then just..write the same script yourself?
- xeromal 4y agoConvenience is the answer to all the "why not do it yourself questions".
- paxys 4y agoWell then you have to pay for the convenience. Can't have it both ways.
- squeaky-clean 4y agoPostman seems to be moving towards not aiming at developers as their main audience. Instead it's for QA, support, managers who want to make some queries against the internal API but can't use curl to do so.
- devmor 4y agoI don't know about other businesses, but the primary consumers of Postman in my organization are QA Analysts, not developers.
- nickstinemates 4y ago> Wtf even is a "local collection runner"? https://learning.postman.com/docs/running-collections/intro-to-collection-runs/ https://learning.postman.com/docs/running-collections/intro-... Basically a way to integrate your API requests into a headless experience, can be used for things like CI.
- deleted 4y ago[deleted]
- atomicnumber3 4y agoWhat is the right way to fund these kinds of tools? Right now, it seems like it only happens a few ways: - be a giant saas and use your "free for personal use" tier as a loss-lead/way to get devs using you, thus wanting to use you at work, then you charge their work. e.g. github. - be linux and be a big enough critical piece to where companies actually fund you directly - pay software engineers oodles of money so that they can have leisure time to maintain the plethora of random FOSS software that's out there - leech off the social safety nets of other countries and let engineers subsisting off ramen in the netherlands write your foss software - play the donation-to-COL arbitrage game and write FOSS from a third-world country where a meager stream of USD donations/purchases can sustain you reliably Pretty much every single one of these except the linux one is pretty awful. And we can't all be Linux. The second least problematic is probably the one where you pay engineers shittons of money and then let them do shit as side projects, but it seems really indirect.
- toomuchtodo 4y ago> be a giant saas and use your "free for personal use" tier as a loss-lead/way to get devs using you, thus wanting to use you at work, then you charge their work. e.g. github. Is not a bad option. Devs won’t pay for tools, but their orgs will. Isn’t that how it should be? My plumber’s employer pays for their Rigid $2k hydraulic copper fitting crimper, for example, because it saves time vs sweating pipes (enabling them to do more jobs, and generate more revenue). Be the hydraulic crimper of dev tools. Expensive, but generating so much value no one batts an eye at paying for it (obligatory patio11 “you’re not charging enough” reference here). Some people will cheap out and pay $100 for the hand crimper and do their crimping by hand; don’t sell to them, they are not evaluating their time value efficiently (or they simply don’t need your tool). For a recent example of this: Docker, going from $12M to $100M ARR within a year as soon as they started charging enterprise users.
- deleted 4y ago[deleted]