- not having to setup a build environment or wait for compilation

- no signals or other dance to setup my data

- class based components, where I could pass arguments to sub-components as constructor args

- scoped styles, two-way binding and other nice to haves.

- not having the limitations of shadow dom (Lit)

- Just be a library I can import anywhere, not be a whole framework.

I wasn't able to find anything that did all of the above. It has a score of 1.08 on the js-framework-benchmark, which is faster than just about every widely known competitor, and most of the faster ones have implementation note "penalties" for not conforming to the benchmark requirements.

Source: https://github.com/eric-frost/solarite

Docs: https://eric-frost.github.io/solarite/docs/

Js-Framework-Benchmark: https://krausest.github.io/js-framework-benchmark/current.ht...

I've used Solarite in production for a few years for an internal work project, but I could use more feedback on the API before I feel comfortable releasing version 1.0.

Comments URL: https://news.ycombinator.com/item?id=50274099

Points: 2

# Comments: 1

https://eric-frost.github.io/solarite/

I think NOT using shadowdom is usually the solution for shared stylesheets. So many of my problems have been solved by just letting the styles cascade.

I also now use AI to build everything and I read less than 5% of the code it writes. I think web components still matter because AI still needs clean and organized code. It can brute force things the hard way, but organized code lets AI move faster with less tokens, less bugs, and less code shipped to the browser.

I assumed Solarite would be at a disadvantage because it's not widely known and AI's aren't trained much on it, but I've found that even the earlier models could use it well, and do so before I released it and before it could have been in any of their training data.

In my experience iframes are far too slow.

https://eric-frost.github.io/solarite/

It supports passing arguments via attributes to constructors. And you can pass complex arguments to nested components without serializing them. No signals and no build step either, just import and use on your regular data. And it's faster than just about all the others.

https://eric-frost.github.io/solarite/

- not having to setup a build environment or wait for compilation

- no signals or other dance to setup my data

- class based components, where I could pass arguments to sub-components as constructor args

- scoped styles, two-way binding and other nice to haves.

- not having the limitations of shadow dom (Lit)

- Just be a library I can import anywhere, not be a whole framework.

I wasn't able to find anything that did all of the above. It has a score of 1.08 on the js-framework-benchmark, which is faster than just about every widely known competitor, and most of the faster ones have implementation note "penalties" for not conforming to the benchmark requirements.

Source: https://github.com/eric-frost/solarite Docs: https://eric-frost.github.io/solarite/docs/ Js-Framework-Benchmark: https://krausest.github.io/js-framework-benchmark/current.ht...

I've used Solarite in production for a few years on a large internal work project, but I could use more feedback on the API before I feel comfortable releasing version 1.0.

Comments URL: https://news.ycombinator.com/item?id=49965000

Points: 3

# Comments: 3

https://eric-frost.github.io/solarite/

There are no signals, proxies, or decorators, or any compilation. You just use plain data. Though the trade-off is that you have to call render() yourself. I prefer it that way though.

- not having to setup a build environment or wait for compilation

- no signals or other dance to setup my data

- class based components, where I could pass arguments to sub-components as constructor args

- scoped styles, two-way binding and other nice to haves.

- not having the limitations of shadow dom (Lit)

- Just be a library I can import anywhere, not be a whole framework.

I wasn't able to find anything that did all of the above. It has a score of 1.08 on the js-framework-benchmark, which is faster than just about every widely known competitor, and most of the faster ones have implementation note "penalties" for not conforming to the benchmark requirements.

Source: https://github.com/eric-frost/solarite Docs: https://eric-frost.github.io/solarite/docs/ Js-Framework-Benchmark: https://krausest.github.io/js-framework-benchmark/current.ht...

I've used Solarite in production for a few years for an internal work project, but I could use more feedback on the API before I feel comfortable releasing version 1.0.

Comments URL: https://news.ycombinator.com/item?id=49921866

Points: 3

# Comments: 1

https://eric-frost.github.io/solarite/

I was also tired of the "all or nothing" of other libraries. Just let me import a js file and then make a class that's a web component. I don't want to setup a whole dang build environment.

With Solarite you just write the markup as a javascript template, change your data however, and then call render(), where it only updates the DOM that should change.

And you can use the component as a tag in your server-rendered page.

https://github.com/eric-frost/taskpilot

https://imgur.com/a/XozIBRb