Replies: 1 comment
-
|
The reasons presented in this article for choosing og made me laugh :#411 "Acknowledging some weak spots, Go's in-proc JS interop story is not as good as some of its alternatives. We have upcoming plans to mitigate this, and are committed to offering a performant and ergonomic JS API. We've been constrained in certain possible optimizations due to the current API model where consumers can access (or worse, modify) practically anything, and want to ensure that the new codebase keeps the door open for more freedom to change internal representations without having to worry about breaking all API users. Moving to a more intentional API design that also takes interop into account will let us move the ecosystem forward while still delivering these huge performance wins." |
Beta Was this translation helpful? Give feedback.
-
Why wasn’t .NET/C# used to develop this project? Is it because .NET/C# isn’t good enough? Are features like dynamic type support, cross-platform compatibility，GC and AOT unable to meet the requirements? Why not just announce the discontinuation of .NET development altogether? Stop everything related to .NET and tell those poor .NET developers to migrate to other platforms!
Beta Was this translation helpful? Give feedback.
All reactions