3 ms·
> My biggest problem of markdown was the specific flavor I happen to be using and the type of cliffs I’d run into, then how to extend them. First time I heard
by rapnie 3y ago
> My biggest problem of markdown was the specific flavor I happen to be using and the type of cliffs I’d run into, then how to extend them.
First time I heard of .mdx and looked up the site [0]. I am insufficiently in the loop of frontend standardization. Now it would be great to get rid of flavors and have one universal approach. In the Docs I read:
> MDX is not coupled to React. You can also use it with Preact, Vue, Emotion, Theme UI, etc. Both the classic and automatic JSX runtimes are supported.
A sibling comment already mentions a Svelte implementation [1]. So I fail to see how this doesn't open a pandora's box of yet more flavors, this time coupled to frontend frameworks. First in .mdx and then incompatible with .md
Extensibility. Yes, I guess, if your stack is supported by any of the existing implementations.
[0] https://mdxjs.com/docs/what-is-mdx/ https://mdxjs.com/docs/what-is-mdx/
[1] https://mdsvex.com/docs https://mdsvex.com/docs
- friendzis 3y agoJSX is evidence that new generation of programmers are not taught engineering. There are very valid reasons why we went for encapsulation and separation of concerns. JSX throws the baby with the bath water and goes back to PHP5 sites with markup and code interspersed. Even authors of JSX cannot make it work reliably in their flagship product. MDX couples JSX with markdown. I cannot see how this yields maintainable source. Sure, spaghetti code is nice for quick, one off scripts, but if you'd volunteer for helpdesk shift to be yelled at rather than fix a bug in 5k SLOC collection of Windows Batch scripts, then maybe you should reconsider mdx.