@wake_up

as for tips for somone new to webcomponents, i think its good to take a look at resources online. i dont know enough to suggest any.

i found that after trying it myself, creating something with vanilla webcomponents was a bit of a pain (and the code looks ugly). so its only natural to lean towards something like Lit or Vue for larger projects.

personally, webcomponents seem cumbersome and thats why i wanted to see if Dim was possible. its an attempt to reduce the complexity.

@wake_up

thanks! im glad you like it :)

> what inspired you to create Dim in the first place?

working with Lit felt a bit like a step backwards when coming from React. the React syntax just seems more elegant to me so i wanted to see if i could do it with webcomponents.

im aiming to see if i can get something that looks and behaves like React, but works natively in a browser without the need to build or transpile. i think in theory it could work.

The previous article in the series has a couple paragraphs at the start to introduce the idea and why:

Modern JavaScript frameworks like React JS and Vue JS have popularized the functional programming paradigm and declarative approaches to web app development. While these frameworks have made creating dynamic web applications more accessible, it's worth exploring the potential of web components in this landscape.

To me it seems more like an exploration and PoC for the purposes of learning than a real alternative to any particular frontend library, but that's just my interpretation. The subject is interesting anyway, even if I won't do this myself in a real world project at work.

@umt

Elm is good.

For this project I specifically wanted to use web components, but in the style of React.

There is no practical use case for this "UI framework". It's a personal learning process.