Hacker News Reader

I mean a realistic version of that comment is that you can use GTP* to make a set of unit tests. Then iteratively write a new version in swift to be bug compliant with the old version using GPT*. Then profit? The question really is why is swift <-> objc bridge so bad you need this software?

View on HN

>The question really is why is swift <-> objc bridge so bad you need this software?

HUH? I don't even understand the question. A bridge is something redundant in itself. It doesn't have to be "so bad" to want to get rid of.

Why keep going through a bridge when you could (after this effort) call the lib directly?

And why maintain the same code in 2 different languages, an increasingly deprecated one, and your new one?

> The question really is why is swift <-> objc bridge so bad you need this software?

Do you want to keep using a UTF-16 backed String type while the world (including Swift) is on UTF-8? (Oh, and I am posing the question to Java too...)

Reply on news.ycombinator.com