3 ms·
Very interesting and wide ranging discussion. Lots of ideas in there too: > Joe Armstrong: What I’d like to see and we don’t do is integrate the language with
by davidw 16y ago
Very interesting and wide ranging discussion. Lots of ideas in there too:
> Joe Armstrong: What I’d like to see and we don’t do is integrate the language within the revision control system because if you rename a variable, and you submit it to the revision control system and say "This is a completely different version of a completely different program but you just rely on the variable because there is no semantics at all just to make it a little bit more readable if you correct a spelling mistake in a comment." The revision control system is a sort of generic and applied to any programming language and that’s really stupid. They need to be much more smart to check what really happening, not this superficial stuff.
> Don Syme: So we’ll have Erlang RCS, Erlang specialized?
Early on, Joe Armstrong talks about Erlang being "object oriented". I don't really agree though, because by the time you actually get processes and things put together - especially with OTP - you have a lot of other stuff running underneath, so you're not just operating at a 'pure' level of sending messages back and forth. And there's lots of boilerplate too. However, it's still a good way of thinking about Erlang from an architectural point of view.