This documentation is confusing.

It says, unbuffered code does not output any code directly. What does that mean?

But in general, what is the difference between buffered and unbuffered code?

Would also be nice if they didn't disable copy and right click on the page too!

This documentation is confusing.

It says, unbuffered code does not output any code directly. What does that mean?

But in general, what is the difference between buffered and unbuffered code?

Would also be nice if they didn't disable copy and right click on the page too!

• javascript
• pug

• maybe someone else is able to help you ;) – Max Bumaye Commented Nov 14, 2014 at 14:51

2 Answers 2

"Unbuffered" means that the code is executed, but the results are not sent to the output buffer.

"Buffered" also means that the code is executed, and the results are sent to the output buffer.

For example, this Jade:

.unbuffered
  - 'unbuffered vs buffered'

.buffered
  = 'unbuffered vs buffered'

Produces this HTML:

<div class="unbuffered">
</div>
<div class="buffered">unbuffered vs buffered
</div>

Please ignore this answer as it is incorrect as pointed out in the ments

I invite you to have a look at matty's answer instead.

From what I understand in the documentation link you shared I'd say there is a major difference:

Unbuffered code is not executed when read, but deferred (it is looks like javascript), which means that the string is post processed.

It seems that they map the string to an internal routine, that is hybrid js + templating language.

Buffered code is on the other hand executed as javascript (first it is preprocessed to escape html). Though it seems to have a different behavior according to which code you put in there.

For example it is said that this:

p='Test' + ' concatenation'

Will result in Test concatenation

But now, you could do this:

p=(function() { return 'Does this really work ?! It seems so'; }())

It will result in Does this really work ?! It seems so.

It simply evals your code and escapes the html.