Comment by axod

  >> printIfNotNull(foo.getBar().getName()); // pointless method

  >> in arc ...
  >> ... aif is a macro that expands this code to
  >>
  >>(let it ((foo 'bar) 'name)
  >>  (if it
  >>      (print it)))

Why is a macro not pointless, while a method/function apparently is? I don't think that makes sense personally. Surely a macro is just a function that's been inlined - which may be better, depending on if you're optimizing for speed or size. Anyone explain?

Also, I'm not sure if this was being serious or not:

  >> Priorities in language design
  >> A Language Should ...

If it was serious, it completely depends on what problem you're trying to solve as to what priorities you're going to have.