Thanks. This would be a lot more useful with a comparison of features or trade offs (e.g. how many resources do you get? does it suspend? what about databases? etc.) instead of just the marketing taglines for each service.
They might be fun for random exploration if you're killing time, but not really a tool
Of course, you could get that same discoverability from language-package manager tool/website, if such systems ever allowed users (not developers!) to tag or otherwise multiply categorize packages, the way that e.g. Spotify allows users to create discoverable public playlists.
If you're already aware of all that, sure, they don't add much information. Concise comparison is pretty difficult...except in cases like this.
I don't know if I agree. I think maybe thorough comparison is difficult. But if you have a list of, for example, open-source alternatives to Postman, just including something like the amount of GitHub stars a project has can go a really long way. Especially if it becomes a list of 20+ projects and many of them have less than 10 stars or are no longer being developed
The difference is basically the difference between a list and a table.
Huge bonus if you use something like a spreadsheet software to make it interactive/sortable
Put it in an airtable. Done.
https://github.com/agamm/awesome-developer-first#deployment-...
I might add the limits too - a cool idea.
For reference, my use case/requirements:
- I want to be able to deploy dockerized apps to an AWS region.
- I should be able to define different process types with different env vars/instance scale
- I don't want to have to worry at all about underlying infrastructure
- I want to be able to pipe the logs out to some other unified logging
- I want to be able to deploy from a CI pipeline.