llama 3.3 70b - does perplexity degrade faster on typescript vs javascript at same context length
client asked this and i have no idea. types add tokens but also add structure. tested small samples (5 files each) at 16k context - typescript sits at perplexity 8.9, javascript at 9.4. seems backwards? anyone tested this more rigorously or am i just seeing noise in small sample
just ran this exact test yesterday on ts vs js at 24k context. ts degradation is noticeably worse - perplexity jumps around 22.8k vs js holding to 24.1k. honestly think it's the type annotations creating more cross-reference patterns that break under q4. what quant are you testing on?
we tested this exact thing on 50 typescript files vs equivalent javascript (types stripped) at 24k context last month. typescript perplexity degrades around 22.1k, javascript holds to 24.8k. is not just type annotations - also imports with type-only imports, generic constraints, interface definitions. all this syntax adds structural complexity without helping model understand semantic meaning