Return to Answer

I'd expect so, yes, because Balpha, aka Benjamin Dumke-von der Ehe, an SE employee, is one of the authors of the specification. And commenting on this post he has confirmed there are plans to support the standard:

I hope to eventually switch Stack Exchange over to this Markdown version. That's still a bit in the future though.

You may also notice another Stack Exchange luminary on the list of authors, although he now has moved on to other things. He blogged about Standard Markdown CommonMark today.

Currently handling [link](foo(and(bar))) is kinda broken, you get link) instead of the expected output in the standard, so it is not like handling that properly in the future will be so terribly bad.

6 years later: Stack Exchange is switching to CommonMark! Yay

Original answer:

I'd expect so, yes, because Balpha, aka Benjamin Dumke-von der Ehe, an SE employee, is one of the authors of the specification. And commenting on this post he has confirmed there are plans to support the standard:

I hope to eventually switch Stack Exchange over to this Markdown version. That's still a bit in the future though.

You may also notice another Stack Exchange luminary on the list of authors, although he now has moved on to other things. He blogged about Standard Markdown CommonMark today.

Currently handling [link](foo(and(bar))) is kinda broken, you get link) instead of the expected output in the standard, so it is not like handling that properly in the future will be so terribly bad.

I'd expect so, yes, because Balpha, aka Benjamin Dumke-von der Ehe, an SE employee, is one of the authors of the specification. And commenting on this post he has confirmed there are plans to support the standard:

I hope to eventually switch Stack Exchange over to this Markdown version. That's still a bit in the future though.

You may also notice another Stack Exchange luminary on the list of authors, although he now has moved on to other things. He blogged about Standard Markdown CommonMark today.

Currently handling [link](foo(and(bar))) is kinda broken, you get link) instead of the expected output in the standard, so it is not like handling that properly in the future will be so terribly bad.

I'd expect so, yes, because Balpha, aka Benjamin Dumke-von der Ehe, an SE employee, is one of the authors of the specification. And commenting on this post he has confirmed there are plans to support the standard:

I hope to eventually switch Stack Exchange over to this Markdown version. That's still a bit in the future though.

You may also notice another Stack Exchange luminary on the list of authors, although he now has moved on to other things. He blogged about Standard Markdown CommonMark today.

Currently handling [link](foo(and(bar))) is kinda broken, you get link) instead of the expected output in the standard, so it is not like handling that properly in the future will be so terribly bad.

I'd expect so, yes, because Balpha, aka Benjamin Dumke-von der Ehe, an SE employee, is one of the authors of the specification. And commenting on this post he has confirmed there are plans to support the standard:

I hope to eventually switch Stack Exchange over to this Markdown version. That's still a bit in the future though.

You may also notice another Stack Exchange luminary on the list of authors, although he now has moved on to other things. He blogged about Standard Markdown today.

Currently handling [link](foo(and(bar))) is kinda broken, you get link) instead of the expected output in the standard, so it is not like handling that properly in the future will be so terribly bad.

I'd expect so, yes, because Balpha, aka Benjamin Dumke-von der Ehe, an SE employee, is one of the authors of the specification. And commenting on this post he has confirmed there are plans to support the standard:

I hope to eventually switch Stack Exchange over to this Markdown version. That's still a bit in the future though.

You may also notice another Stack Exchange luminary on the list of authors, although he now has moved on to other things. He blogged about Standard Markdown CommonMark today.

Currently handling [link](foo(and(bar))) is kinda broken, you get link) instead of the expected output in the standard, so it is not like handling that properly in the future will be so terribly bad.