Conversation

Notices

1. Embed this notice
   Matthew Lyon (mattly@hachyderm.io)'s status on Wednesday, 22-Jan-2025 03:55:54 JST Matthew Lyon

   a common reaction to this complicated js build tooling is going buildless, and instead of `import '/foo.css'` it's now recommended to write your css & html like:

   return html`
   <style>
   div {
   background: ${color};
   }
   </style>
   <div>${content}<div>
   ` }

   and folks, this is in many ways worse

   I'm not going to explain to you why putting code in strings is bad. I detest how popular this pattern has become https://hachyderm.io/@mattly/113840282345132644

   • Embed this notice
     Jenniferplusplus (jenniferplusplus@hachyderm.io)'s status on Wednesday, 22-Jan-2025 04:16:14 JST Jenniferplusplus

     in reply to

     @mattly oh, God

   • Embed this notice
     Jenniferplusplus (jenniferplusplus@hachyderm.io)'s status on Thursday, 23-Jan-2025 02:52:24 JST Jenniferplusplus

     @mattly so it's really convenient for the framework author, and a high powered automatic foot gun for the framework user

   • Embed this notice
     Erin 💽✨ (erincandescent@akko.erincandescent.net)'s status on Thursday, 23-Jan-2025 04:32:12 JST Erin 💽✨

     in reply to

     @mattly you know, a few decades ago I did some webdev in the much-maligned Zope where the templating language (ZPT/TAL) is a bunch of namespaced elements/attributes jammed into (X)HTML and ever since I have been convinced that it is obviously true and correct that any templating system you use needs to be language aware.

     And then I watch people write Helm charts and I despair because shoving together YAML and Go text/template is the worst possible combination I have ever seen.

     Haelwenn /элвэн/ :triskell: likes this.