Just because you change the acronyms doesn't mean that you can completely forget about CI/CD. It's still relevant. Even more so with the newer technologies. You'll probably use different build tools and testing tools. But everything else is still the same.
You will, and I'm certainly not objecting to the use of CI once you know what product you're building and what its architecture will look like. But the whole point of this discussion is that you don't know that in this phase of startup development. There is a non-trivial chance that you will have to swap out your entire tech stack or drop whole components from the product. Building extensive infrastructure around code that gets run 2-3 times and then deleted entirely is a waste of time.
If you've started building software that you're going to have scrap that quickly, your problem isn't with the tools. You've messed up big time with planning. Either way, you're still going to need CI/CD.
