Live data from Hacker News

Show HN: Cami.js – A no build, web component based reactive framework

github.com

11–20 of 36 posts

Re: Show HN: Cami.js – A no build, web component based reactive framework

#12
post #11

I see many points in common with https://www.arrow-js.com/ Probably that focus on components could be the only difference

Interesting! Many points are indeed similar. Apart from components, Cami also has immutability built-in and state management.

Re: Show HN: Cami.js – A no build, web component based reactive framework

#14
Nice work, love the use of reactivity via observables and pub/sub stores (some of my favourite abstractions)

Some feedback from first glance is “type inference” could be better, which would help prevent a lot of foot-guns. Consider the example code here:

    this.count = this.observable(0);
Does this allow “count” to be inferred as a “number” type in the rest of the code? There might be a way to allow JS to easily infer the types, without requiring a build step…

Re: Show HN: Cami.js – A no build, web component based reactive framework

#15
post #14

Nice work, love the use of reactivity via observables and pub/sub stores ( some of my favourite abstractions ) Some feedback from first glance is “type inference” could be better, which would help prevent a lot of foot-guns. Consider the example code here: this.count = this.observable(0); Does this allow “count” to be inferred as a “number” type in the rest of the code? There might be a way to allow JS to easily infe…

This is great feedback, thanks! I think there’s something around JSDoc types that can accommodate this. Something I’ll put as a milestone before v1.

Re: Show HN: Cami.js – A no build, web component based reactive framework

#17
lit-html author here. I'm glad the template library is useful for you!

Question regarding interop with other web components: I don't see how to create reactive properties on elements. Can they receive data from parents via property bindings? Ie, could a Lit element pass data to a Cami element?

Re: Show HN: Cami.js – A no build, web component based reactive framework

#19

What's the advantage of not having any build steps? For me personally, it's an instant turn-off, as I'll never use an untyped library.

faster and simpler deployment, e.g., rsync to your webserver, no need to wait for the build step.
Post reply on HN