|
|
|
|
|
by Rohansi
39 days ago
|
|
They said the prototyped in a few languages before settling on Go. Based on what you said it sounds like they didn't do a great job at that and stuck with their decision anyway. > Also to note that it was pointed out that Native AOT wasn't up to the job, again something that both Java and C# failed not having done it properly from day one. It's been working fine for a few years now. The only problem I know is there is little to no reflection allowed (by design) so a lot of code out there is not compatible with it yet. Not sure if that's what turned the TypeScript team away from it. |
|
https://youtu.be/UJfF3-13aFo?t=1453
As for the AOT part, one would expect that being all Microsoft, they could work together to fix whatever were the issues with Native AOT.