DEV Community

Discussion on: Components are Pure Overhead

Collapse
 
ryansolid profile image
Ryan Carniato • Edited

This is so hard because in terms of production Marko is rock solid but I mean we all want to play with the new toys. And the new Marko brings a lot of cool things. We are still looking for later this year, and hoping to do a beta release this summer.

Maybe we can meet half way. Projects like Vite + HMR have made the dev experience a lot smoother. At some point of the process we are backporting the new Marko syntax back into Marko 5. This will mean while you won't get to leverage the technology you will be able to slowly migrate old projects, or in your case use the new syntax so the bump to Marko 6 won't require a code change to benefit. Obviously writing new transformations for the compiler is a time investment against working on Marko 6 but it sounds like there is interest here.

I will look at what it takes to get this out.

Collapse
 
drsensor profile image
૮༼⚆︿⚆༽つ

What approach do Marko lsp-server use for the type checking going to be?

  • Is it wrapping up a bunch of stuff like tsserver, vscode-css-languageservice, etc just like in Svelte langserver? or
  • Roll up Marko's own type checker? (mean it doesn't depend on 3rd party which can be more perfomant)
Thread Thread
 
ryansolid profile image
Ryan Carniato

I was waiting for more information from Dylan but he's out this week. To my knowledge probably something similar to Svelte. We see the limitations and were sort of surprised by them, but if that is enough to satisfy the requirements and it's quicker it can help perception a lot. Getting TS in the templates would be a huge win as it is and we want to prioritize the architectural considerations first.