I’m creating a JavaScript UI framework for my own projects. It’s a learning journey and I’d like to share my progress.

I’ve written some blog posts about my progress so far:

  1. Functional Web Components - https://positive-intentions.com/blog/dim-functional-webcomponents
  2. Functional Todo App - https://positive-intentions.com/blog/dim-todo-list
  3. Async State Management - https://positive-intentions.com/blog/async-state-management
  4. Bottom-up Browser Storage - https://positive-intentions.com/blog/bottom-up-storage

Note: The UI framework is far from finished. I want to share progress to see if there are any outstanding issues I’m overlooking.

  • MonkderVierte@lemmy.ml
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    14 days ago

    Ugh, please no. Please don’t paint UI-elements via JS, if you’re not forced to. It makes for a poor experience for most users, not to mention accessibility.

    • moseschrute@lemmy.ml
      link
      fedilink
      English
      arrow-up
      2
      ·
      14 days ago

      I spent a lot of time early in my career working on some UI component libraries that I ultimately deemed a failure. However, I learned a lot from that. I’ve found that as I’ve settled into a more senior dev role, it’s become harder for me to experiment.

      What I’m trying to say is that best case, you come up with something cool, and worst case, you learn from your mistakes and apply what you learned to the next project!

    • JakenVeina@lemm.ee
      link
      fedilink
      English
      arrow-up
      1
      ·
      12 days ago

      What are you considering as “paint[ing] UI-elements” in this context? I don’t see anything I would describe as “painting” in the code snippets ay those links.