You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Potentially a huge amount of work, but it would be great to see an RTC implementation that was more than an adapter to the c-native reference implementation. Reasons include gaining Go's safety and compilation benefits, independent failure / exploitation surface area, and could likely be significantly easier to understand.
The text was updated successfully, but these errors were encountered:
Agreed for those potential benefits (and having another true independent implementation in the ecosystem would be good for the spec)... though it would indeed require an enormous effort.
Right now, having made WebRTC work in Go at all has been wonderful for getting other things off the ground :) But, perhaps in the future!
Potentially a huge amount of work, but it would be great to see an RTC implementation that was more than an adapter to the c-native reference implementation. Reasons include gaining Go's safety and compilation benefits, independent failure / exploitation surface area, and could likely be significantly easier to understand.
The text was updated successfully, but these errors were encountered: