Looking for a technical co-founder for a travel startup

I agree with Raj. Good developers who are looking for an opportunity, want to work on something they care about. I think he's very clear and open about the project from both technical and commercial perspective.

While assume Petrovn means well, I personally wouldn't worry about the tone of voice.

A couple of years back I worked at https://www.spoorgloren.nl (Dutch website), a consultant related to rail mobility and energy efficiency. Worked on a prototype that the NS now fully implemented that is making trains be more on time and drive more efficient at the same time.

We had some discussions about tools that could perhaps provide fully door-to-door service. So not only the flight, but also the taxi/bus, perhaps even hotel, etc. Didn't take much action on it at the time. To counter Petrovn on the age and lack of money in traveling; there is travel in business, and there is money to be made if you can make it more efficient (or perhaps green, more convenient, etc).

Anyway, while he won't be your CTO, he might be interested to chat with you if you have ideas in that area and looking to partner in the Netherlands in some way.

most people that are into "traveling" and understand the pain points are going to be 20 year olds with no money, hence the understanding of pain points :)
you definitely don't want one of them to be CTO as for every "bill gates" there are 10 Million that think they are but are not even remotely on that level.
When you use a company for a project system design, implementation and time are not important to you as you pay on delivery to a working product, but when you work with someone "inhouse" the CTO (even if you are calling it something else) is responsible for all of this and you may lose a lot of time to realize that the system will go nowhere or you may realize that on top of the wasted time what you think is a 80% build (a lot of nontech founders end up there) and you need to just find someone to finish it or to invest a little bit more time and resources, but in reality, is actually total waste, as it is badly designed and it will never work.
Just be careful and luck helps a lot in this situations :)

you are correct, the most inexperienced devs will give up, but you do not actually want them around unless you have someone very good at organizing work for junior devs.
and the experienced people will give up even if they have passion for whatever they build if they don't see the project moving forward (before the development is even 20% done) as they will have options and definitely prefer getting paid for something not that interesting than building something that will go nowhere.