this post was submitted on 29 Sep 2024
3 points (80.0% liked)

Programming

17424 readers
51 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] umt@lemmynsfw.com 1 points 1 month ago (2 children)
[–] xoron@mastodon.social 2 points 1 month ago (1 children)

@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.

[–] umt@lemmynsfw.com 1 points 1 month ago

Cool. Learning is good.

[–] TehPers@beehaw.org 2 points 1 month ago (1 children)

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.

[–] xoron@mastodon.social 2 points 1 month ago

@TehPers @umt

> PoC for the purposes of learning

yeah thats right.

i want to see if creating some kind of thin-transparent-wrapper like this, could make it so i dont have to update it as a dependencies. consider that we recently got react 19. this will be followed by a scramble by many to use the latest and most stable version.

i cant guarantee any stability in my current progress, but in theory, by relying on the underlying web component from the browser, it becomes future-proof.