That's maybe important and interesting to developers, but the value proposition of urbit is to the regular computer user. John Doe doesn't care what names or concepts are used in ECMAScript, he just cares that his browser works. John Doe doesn't care what names or concepts are used in the urbit stack, he just cares that his personal server works

The value proposition depends on developers, so mentioning the mysteries they have to go through is relevant to making a summary. It's a huge part of what makes urbit urbit.