Swift

Swift neo will take on a similar roll where it will become more of a kind of facilitator, like a framework that you operate using. But if you're just writing a service ite ap using something like vapor, you don't necessarily need to be so aware of the kind of swift neo under pinnings any more. Because you're just using asinca weight. And i think the same thing can be true on the klin side as well. Like we can build systems using, for example, reactive program or other techniques, but then on the api level, you just have an asing function that you call with a weight, and that's it,. So itis