Show HN: I built a backend so simple that it fits in a YAML file
1–10 of 80 posts
Re: Show HN: I built a backend so simple that it fits in a YAML file
#2Neat.
Re: Show HN: I built a backend so simple that it fits in a YAML file
#3> If you ask 10 backend developers what you should use for your app’s backend, they will probably come up with 10 different stacks.
And now they can come up with 11!
Re: Show HN: I built a backend so simple that it fits in a YAML file
#4Thoughts:
1) put the “# Short syntax for string type.” comment in your docs on your homepage example. When I first saw the “price” element I thought it was a jsonb field or something
2) why the emojis? So confused. Are those an alternative to a “dash” for entities? Do I need todo those? Do they set the favicon for that rest page? Note: it looks like it messes up indentation alignment. If it’s trying to be cute, I would deprioritize it
3) a “curl” command example on the homepage would make it a bit easier to grok the value of how simple your backend is
4) where does the data get stored? SQLite? Duckdb?
Re: Show HN: I built a backend so simple that it fits in a YAML file
#5These abstractions are great but are contributing to brutal de-skilling.
Re: Show HN: I built a backend so simple that it fits in a YAML file
#6[flagged]
Re: Show HN: I built a backend so simple that it fits in a YAML file
#7Do you mean simple or easy? It seems like you actually mean to say easy.
Re: Show HN: I built a backend so simple that it fits in a YAML file
#8These abstractions are great but are contributing to brutal de-skilling.
What do you mean?
Re: Show HN: I built a backend so simple that it fits in a YAML file
#9> If you ask 10 backend developers what you should use for your app’s backend, they will probably come up with 10 different stacks. And now they can come up with 11!
those other 10 people don't know what they are talking about!