1. 20
  1. 33

    title is misleading; this is an experimental early WIP by someone who is (afaik) not connected to svelte, rather than either an official migration of the svelte compiler to rust or a working alternative compiler.

    1. 28

      This is an interesting study in how a title that’s completely sensible in one context might be misleading in another. “Svelte compiler rewritten in rust” is perfectly descriptive as the title of some random person’s GitHub project, but becomes misleading when transplanted into a post on a link aggregation site.

      Orange sites with strict “use the original title; don’t editorialise” rules may wish to take notes.

      1. 2

        Personally i read it as the first version right off the bat. I didn’t even understand what the comment above meant. Only when you mentioned it, I saw how else it could be read.

    2. 4

      One really cool implementation feature of the Svelte compiler is that it uses code-red to generate JS code by basically writing a template of the desired generated code. I’ve been looking for a similar tool in Rust for a compiler I’m playing around with. Does anyone know of anything comparable?

      I thought this might be taking a similar approach, but it looks like this project doesn’t even generate any code yet.

      1. 3

        Deno showed a lot of progress, and still has a lot of progress but I’m a little disappointed with how much it has seemingly lagged. As soon as I tried to use it for any web development I always ran into how pervasive node is and how non-standard most Typescript implementations are. I forgot the details but I was using an Adobe design framework that had a Typescript implementation but deno was pretty strict and the exported modules were not doing something in the language spec.

        It was a huge hindrance to adoption and ultimately I just went back to using golang for the backend and nodejs for the frontend. I was hoping to use Typescript throughout, it would have been a game changer but to do so you need to really roll your own frameworks. Hopefully someone will come up with a solution that lets you use legacy frameworks seamlessly with Deno.

        Svelte was another thing I couldn’t use so hopefully this solves that, but there’s so much out there that isn’t supported it seems like one framework or library you need means pretty much either taking on the burden of writing or introducing the mess of nodejs into the project and at that point might as well just go nodejs all the way.

        1. 3

          Not sure if you’ve seen this, it outlines Deno’s recent intent to improve compatibility with node:

          https://lobste.rs/s/gmhj3l/big_changes_ahead_for_deno

          1. 1

            It was a huge hindrance to adoption and ultimately I just went back to using golang for the backend and nodejs for the frontend.

            I’m often confused at first at these types of comments, e.g. (“wait why/how would you use nodejs in front-end”), but then I realize what you meant.

          2. 3

            The project is open to naming suggestions!

            Rustvelte comes to mind.