cami.js VS chat-app

Preact requires a build step otherwise you don't get JSX and you have to build applications a la mithril.js mode:

> const app = h('h1', null, 'Hello World!');

With Web Components no build step is required and you're still able to build JSX'ish code. See the code below this section: https://github.com/kennyfrc/cami.js#key-concepts--api

Yes, the lib's great!

Unfortunately I haven't thought much yet about interoperability with other web components libraries like lit. I imagined folks would choose just one web component library over the other.

That said, you can initialize reactive properties(1), but property bindings won't work if there's a parent LitElement (as my reactive properties need to be called with either a .value method or an .update method for getting and setting respectively).

As of the moment, what's possible is interop with other cami elements using a store, and in a future version, i'm considering a richer event system for external javascript code to listen to.

---

(1) Initializing is possible with observerableAttr: https://github.com/kennyfrc/cami.js/blob/master/examples/008...

The author is getting a bit of heat, and I think rightfully so. Here is the "tool" he's all bragging about: https://github.com/kennyfrc/cami.js/blob/master/src/cami.js

The whole thing is 250 Loc half of which is comments. And not to discount on that (Redux itself is not that big, though the ecosystem is). But this tool/project could be just a few blog posts where the author explains the patterns/libraries he is using.

It also doesn't help that his blog post/tool has the highest concentration of buzzword language you can expect. Please don't do that.

I built a serverless SaaS no-code/low-code platform which could be of interest: https://saasufy.com/

You just need plain HTML which can be deployed online with something like GitHub pages.

I've built a few apps with it including a simple real-time chat app which supports both group chat, private 1-on-1 chat with an account system, OAuth via GitHub... The entire app is only 260 lines of HTML markup. See: https://github.com/Saasufy/chat-app/blob/main/index.html

It comes with around 20 generic declarative HTML components which can be assembled in complex ways: https://github.com/Saasufy/saasufy-components?tab=readme-ov-...

There is a bit of a learning curve to figure out how the components work but once you understand it, you can build apps ridiculously quickly. The chat app only took me a few hours to build.

I've been helping a friend to build an application related to HR with Saasufy and I managed to get the basic search functionality working with only 160 lines of HTML markup.

>I built a chat app with both group chat and private chat (with access control) using only plain HTML; only ~250 lines of HTML markup for the entire thing: https://github.com/Saasufy/chat-app/blob/main/index.html

I think I know what you mean, but we clearly have different definitions of "plain HTML." Mine wouldn't involve 9 javascript files. :-D

Either way, I'm interested and will check out what you made!

The repo for the chat example I alluded to in this guide can be found here: https://github.com/Saasufy/chat-app and is hosted here: https://saasufy.github.io/chat-app/ (you can log in with GitHub by clicking on the link at the bottom of the log in form).

Web Components are extremely powerful. I built a chat app with authentication with 2 different blockchains, GitHub OAuth login and access control using only 120 lines of HTML on a single page with no framework:

https://github.com/Saasufy/chat-app/blob/main/index.html#L23...

You can try the app here (if you have GitHub): https://saasufy.github.io/chat-app/

The backend is serverless built using Saasufy.com - The platform/startup I'm working on currently: https://saasufy.com/

You can log in via GitHub OAuth (also implemented with HTML tags).

The source is here, that's all of it, there is no custom backend logic: https://github.com/Saasufy/chat-app