Don’t build your own framework

Terminal command "rm -rf .git", surrounded by random characters.

In 2019, I wanted to create a website that followed our custom design with smooth animations and interactions. I looked at UIkit (opens in new tab) , but I didn’t choose it for two reasons:

  • It has its own take on design
  • It doesn’t meet my requirements for “fluid”

This led me to search for other frameworks that, unlike UIkit, only provide basic JavaScript functionality, allowing you to style and animate however you want. I didn’t find anything. So, naturally, I decided to do it myself (opens in a new tab) .

I’m developing the framework in parallel with the website I’m developing and it’s great. I was able to get the code just right and implement what I needed. I took some inspiration from UIkit, but stuck with my main idea.

Later, it was found that the efficiency was not high, so I decided to refactor. But because I’m developing that framework and using it at the same time , I’m not only redesigning the framework, but also the website. Other than that, I’ve tried to make this work for as many use cases as possible. What if you use React ? What if you don’t? What if you use jQuery? What if you don’t even know JavaScript well?

At this point, my enthusiasm began to slowly wear off. Unconsciously, I put myself in a position to want to solve problems that didn’t exist yet and solve them perfectly. But I still believe that in the end, it will be “worth it”.

Then, our team started to grow. I am no longer the only one working on that site. Since it uses my framework, I had to get newbies to use it. That means I have to write a README, followed by documentation, example usage, etc. Still, we still need to clean up a few things in Slack.

As our team grows, so does our workload. This caused the framing work in parallel with the website to transition to framing work on weekends and early mornings.

However, I continue. I have (and still have) a habit of abandoning projects, so I decided to at least reduce the framework to small, organized snippets of JavaScript that can be downloaded via npm . But do I use custom element (open in new tab)

The post Don’t Build Your Own Framework first appeared on Lenix Blog .

This article is reprinted from
This site is for inclusion only, and the copyright belongs to the original author.

Leave a Comment