openapi VS plutus-starter

I wonder if there is a format for API -> client automation that can be good enough, in the end Stripe have a rest API, with enough description it should be possible.

Okay so after a quick google it appears Microsoft are the "Simpsons already done it" of the programming world: https://github.com/Azure/autorest/

It'd probably be a good idea to add an Elixir backend for that and point it at Stripe's API here: https://github.com/stripe/openapi

Our specs were split between several YAML spec files. It looked like a good idea when we did that - large files are not fun to work with. The problem is that very little in the OpenAPI ecosystem was built for multiple files. I strongly recommend that you will save yourself the pain and go the mono-file route. If Stripe can have a 4.5MB spec file, so can we.

This is pretty bad advice - you might not need a node to write dapps, but you'll sure as hell want a local Plutus dev environment for the smoothest experience. Take it from someone with an M1 - the setup process is a pain, compile times are poor, and it'll be difficult to get your language server up and running for proper syntax highlighting. Some repos like https://github.com/input-output-hk/plutus-starter don't seem to work even when Nix is configured to run it on Rosetta 2. Like the other commenter, I've resigned myself to ssh tunneling into a development Linux NUC, which has its own annoyances.

This what you wanted? https://github.com/input-output-hk/plutus-starter

I love how the Cardano devs are making Plutus Dev Env as easy as possible to install and use. Just install Docker on your OS and:

Feel free to check the Cardano starter example project on Github