|
|
|
|
|
by dwilding
2971 days ago
|
|
I'm building the API for my side project on StdLib, and the experience has been great so far, for many of the reasons you mention - so thank you! For comparison, I'm also building part of the backend on Webtask [1], which provides similar functionality to StdLib (i.e., serverless Node.js functions). Webtask is also very nice to use, but I find StdLib more suited to shipping a public-facing service. [1]: https://webtask.io/ |
|
If you don't mind me asking; are there things you like to do with Webtask that you think we could improve with StdLib? You mention a strength of ours is creating public-facing services, but the majority of customer use cases are actually private (internal) APIs. Is there anything we can do to make this more clear? (Edit: I mean more clear as to the ability to do both.)