3 ms·

What's your reasoning behind the choice of markdown? To quote yourself - > What began as elegant HTML, CSS, and JavaScript has devolved into build systems dem

What's your reasoning behind the choice of markdown? To quote yourself - > What began as elegant HTML, CSS, and JavaScript has devolved into build systems demanding hundreds of dependencies just to render a page If HTML is so elegant, why isnt nuejs not using it? --- On the similar line, if you're so much for web standards, why are you recommending the use of Bun which breaks so much of standards in the name of speed?

tipiirai 2y ago
HTML for layout, Markdown for content. How else could it be?
- bitpush 2y ago
  The entire nuejs route is built using markdown. https://github.com/nuejs/nue/tree/master/packages/examples/simple-blog/welcome https://github.com/nuejs/nue/tree/master/packages/examples/s... which is totally non-standard. Super common, but non-standard. You compiled the markdown to html using a tool (another non-standard item) You dont get to claim "standards-first" framework and then use non-standard technology and workflow.
  - tipiirai 2y ago
    In Nue you're literally writing standard HTML, CSS and JavaScript when developing websites. Your Markdown- based content generates semantic HTML. Your styling is pure CSS with modern features like nesting and container queries. JavaScript remains vanilla JavaScript.
    - igravious 2y ago
      I'm not literally writing" standard HTML, I'm literally writing Markdown and the tool you've yet to fully realise is generating* HTML from the Markdown I'm literally writing.
      - tipiirai 2y ago
        You nailed it. Content separated from the structure. As it should be.
      - klibertp 2y ago
        The issue here is that the GP probably doesn't consider writing content to be related to developing the website. Which is fair. It's one way of looking at it. Once, a really long time ago, I made a website (e-shop) where the content was written in an XML file, sliced and diced by XSLT via a little PHP script. My job was to write the (X)HTML for the layout and XSLT for data extraction - the content was something my client provided. If they provided the content in Markdown, I'd use markdown-to-html converter instead. Crucially, if I were provided with content in HTML, I'd also handle it (most likely not by directly pasting it into the page, though). I'm sure you can change the format in Nue trivially and write your posts in HTML if you want (right, @tipiirai?)

tipiirai 2y ago

HTML for layout, Markdown for content. How else could it be?

bitpush 2y ago
The entire nuejs route is built using markdown. https://github.com/nuejs/nue/tree/master/packages/examples/simple-blog/welcome https://github.com/nuejs/nue/tree/master/packages/examples/s... which is totally non-standard. Super common, but non-standard. You compiled the markdown to html using a tool (another non-standard item) You dont get to claim "standards-first" framework and then use non-standard technology and workflow.
- tipiirai 2y ago
  In Nue you're literally writing standard HTML, CSS and JavaScript when developing websites. Your Markdown- based content generates semantic HTML. Your styling is pure CSS with modern features like nesting and container queries. JavaScript remains vanilla JavaScript.
  - igravious 2y ago
    I'm not literally writing" standard HTML, I'm literally writing Markdown and the tool you've yet to fully realise is generating* HTML from the Markdown I'm literally writing.
    - tipiirai 2y ago
      You nailed it. Content separated from the structure. As it should be.
    - klibertp 2y ago
      The issue here is that the GP probably doesn't consider writing content to be related to developing the website. Which is fair. It's one way of looking at it. Once, a really long time ago, I made a website (e-shop) where the content was written in an XML file, sliced and diced by XSLT via a little PHP script. My job was to write the (X)HTML for the layout and XSLT for data extraction - the content was something my client provided. If they provided the content in Markdown, I'd use markdown-to-html converter instead. Crucially, if I were provided with content in HTML, I'd also handle it (most likely not by directly pasting it into the page, though). I'm sure you can change the format in Nue trivially and write your posts in HTML if you want (right, @tipiirai?)