5 ms·
I agree with you, but sounds like a rough problem: https://danielchasehooper.com/posts/why-swift-is-slow/ https://danielchasehooper.com/posts/why-swift-is-slow
by yAak 1y ago
I agree with you, but sounds like a rough problem:
https://danielchasehooper.com/posts/why-swift-is-slow/ https://danielchasehooper.com/posts/why-swift-is-slow/
- saagarjha 1y agoThe author is welcome to add type annotations if they want…?
- grandempire 1y ago?? No other language times out error checking. This is insanity.
- saagarjha 1y agoNot regularly but many languages have type systems that are algorithmically worse, like TypeScript
- 9dev 1y agoAs a user, I couldn’t care less about the algorithmic beauty of the type system if it works, lets me type complex things reliably, and is fast enough to stay out of my way. Does it do that by being a mess of duct table and plywood? Totally fine for me.
- saagarjha 1y agoSure, but often the duct tape and plywood makes it difficult to make things that are reliable and stay out of your way.
- troupo 1y agoAnd yet TypeScript doesn't fail with a cryptic nonsensical error just because you have the impossible component with an unfathomable number of two nested lists, like in SwiftUI.
- saagarjha 1y agoAlgorithmically worse doesn't mean worse in practice
- grandempire 1y agoCan you show a common line of type script that will take exponential complexity for typescript to resolve?
- saagarjha 1y agoI think you misunderstood my comment.
- troupo 1y agoEveryone misunderstood your reply. Perhaps it was a pure academic reply? Because reality always trumps theory.
- saagarjha 1y ago> Perhaps it was a pure academic reply Yes, exactly.
- grandempire 1y agoMy understanding is you are saying TypeScript has a similar complexity problem in its type system as Swift. I am wondering if you have a common example that would timeout or have problems. If not then I struggle to see what similarity you are seeing. (Genuine question, I am interested in what other languages do)
- saagarjha 1y agoNo, I'm saying it has a worse system than Swift's. The point I'm making is that they've designed things such that the normal case doesn't hit this, while Swift keeps adding APIs that exercise the worst of their type system.