3 ms·

can you please elaborate on what you'd like to see improved in OTP?

• evgen 17y ago
  Documentation for starters. There are a ton of hidden gems down there in the weeds, but until you really grok the whole system they are quite hidden. I needed to have a worker query its supervisor for the start args of all of its running children once. The info existed and eventually I found it (sys:get_status called on the supervisor and then pulling data out of some heavily nested tuples), but it was not a part of the standard supervisor calls and eventaully someone pointed me to the sys module; digging in here taught me a lot about how things work, but it is not easy to find if you don't know where to look. OTP is a lot like Rails, there is a steep learning curve but once you really understand how it works you can do a lot of very cool things with the available tools.
• jerf 17y ago
  You end up with a lot of unfactorable redundancy in the things that implement the behaviors. You end up having to do a lot with records, and the syntax for dealing with them is very verbose. The distinction between handle_info and handle_cast is a bit odd. It's a lot of little things, many of which are actually Erlang-the-language/syntax, that adds up to an experience that is better than anything I know when you're hitting the strengths of the system, but still could use some improvement.