[erlang-questions] user interface, xml, configuration files, reflection

[Hugh Perkins]

Erlang rocks.  It makes a lot of things that are insanely hard in C#
look trivial, ie threading, controlling distributed applications,
updating distributed applications without restarting everything,
message queuing across a network, etc ...

There are some things that I'm used to being able to do in C#.  What
are the options for porting these to Erlang?  They are:

- user interface.  Mostly I use a web interface, because it makes it
easy to update, nothing to distribute to users' machines.  Thoughts
for user interfaces in Erlang?

- xml and / or configuration files.  In C# I store configuration in an
xml file which I read at program start, and write as it changes.
Reflection handles reading/writing to the xml file automatically

- reflection.  Reflection is *very* powerful.  It takes a lot of the
tedium out of programming, letting one concentrate on the interesting
bits.  What are the options for reflection in Erlang?

The other stuff, Erlang rocks at.  I'm a little wary of the lack of
UTF-8, but it looks like it's in the pipe?  As far as rpc, asking
whether erlang can do rpc is like asking if eskimos have snow ;-)