Yes, the plan is to re-implement inet on top of socket. I guess that we will still need to keep the old inet and inet driver around for backward compatibility reasons for some time. There is probably code out there that accidentally or deliberately depends on implementation details of the old inet, for example the fact that sockets are ports.

Yes, definitely not in OTP 22.

It’s really too early to say, but given OTP’s focus on backward compatibility and how much hard work it is to implement socket code reliably on all platforms, I would expect socket and inet to exist side by side for a long time.

Looking forward to the new socket interface!

What’s the projected timeline for socket replacing inet, I imagine it won’t happen in OTP 22? I haven’t tackled inet yet in enigma because I was hoping to avoid doing it with ports.