Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Why would it be "sweet"? There is no gain for the user.


I built a high end desktop after exclusively using desktops for a decade because Unity WebGL builds are so awful. It is the slowest, most opaque and buggiest build chain I have used since I made Flash games.


I expect it would replace the need for the burst compiler, and likely reduce the complexity of the job system (especially its need for special types.) There is also an observed performance gain switching from IL2CPP to CoreRT, which would be 100% free.


Was that performance gain proven with benchmarks across all hardware platforms that Unity supports as deployment target?


I think the idea is to consolidate effort to a single C#-to-native path that is not proprietary.

I agree the the Users of Unity may or not see gains in the short term




Consider applying for YC's Winter 2026 batch! Applications are open till Nov 10

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: