Cannot we use something like Solidjs instead of Preact

[kawpii]

Solidjs : https://solidjs.com/

[lucacasonato]

Not right now, no.

[verlor]

are there any plans on the near future to support other/s frameworks ?

[lucacasonato]

If the given framework provide the same pluggability as Preact (https://preactjs.com/guide/v10/options) which is required to make islands work, I can consider it.

[shishkin]

What is the dealbreaker in pluggability? Astro supports Solid. How is their islands implementation different?

[marvinhagemeister]

They have written a custom compiler that converts .astro templates into the required formats. Afaik they don't allow you to mix and match server rendered content and client side one like we do.

[adamzerner]

I suspect that supporting other frameworks would add a good deal of complexity and decrease velocity a good amount. Astro is the only metaframework I know of that supports multiple frameworks. Personally, I prefer and suspect it'd be best for the Fresh team to say no here.

[andykais]

If we ever get to a place which supports multiple jsx compilers, these discussions over in the solidjs repo may be helpful:

• Deno example? solidjs/solid#873
• Have you ever considered porting solid to deno? solidjs/solid#332

[robvanvolt]

What about nano-jsx? Is this a potential replacement for preact?
https://nanojsx.io/

[saolof]

What concrete advantages does Solidjs offer over Preact? The latter is much more mature, and while solidjs is faster than react, the perf advantage over preact seems to be smaller than the standard deviation in measurement results according to this benchmark with solid having a worse worst-case performance, while also requiring a more complex toolchain:
https://webcomponents.dev/blog/all-the-ways-to-make-a-web-component/

The entire point of Deno is to require zero build tools (not even a typescript compiler since the runtime will just accept .ts files and jsx), which fresh also aims for, so moving to a framework which requires a compiler feels like a step backwards in that sense. You should just be able to copy the raw source files from the git repo to the runtime container.

[shishkin]

I'm not sure if web components context is different, but in this benchmark Solid shows pretty consistent and significant performance gain over Preact.

Besides performance, Solid might be better positioned for Fresh with its island architecture since Solid is aiming at eliminating need for component hydration.

[saolof]

Ah, the performance metrics are different and consistent between the two. Preact wins by a small margin on startup time and time to interactive, while solid does wins on RAM usage and operations on collections of ~1000 elements, while both contribute negligibly to bundle size.

By eliminating hydration, do you mean having streaming SSR?

[shishkin]

By eliminating hydration, do you mean having streaming SSR?

@ryansolid describes it like this in https://dev.to/this-is-learning/resumability-wtf-2gcm:

This is known as Partial Hydration; you may have seen a version of this technique, Islands, in frameworks like Marko, Astro, or Fresh. The difference is resumable frameworks can do this at a sub-component level, much smaller than Islands, and they can do it automatically.