The story
Componyx started as a personal project, driven by curiosity, creativity and a desire to build things. It began with a small collection of UI components and a browser compatibility library, similar in spirit to what jQuery was used for: making web development easier and faster. As the project grew, so did the ideas behind it. Eventually, I started writing the first lines of what would become Bindary, a data-binding layer built around plain HTML and JavaScript. Over the years, the web development landscape changed considerably. Frameworks became more powerful, package managers became standard and applications increasingly came with layers of dependencies, build steps, tooling and abstractions. Meanwhile, Componyx kept growing.
Rather than moving away from the codebase I had built, I chose to embrace it. I kept refining it, adding to it and maintaining control over how it worked. The result was a client-side codebase built almost entirely from its own components and libraries, with very few external dependencies. That wasn't originally a statement against frameworks. It was simply the way I preferred to build software. Today, that choice feels more relevant than ever. Modern web development can require developers to learn a framework's mental model, understand its tooling, manage its dependencies and work through multiple layers of abstraction before getting to the thing their application ultimately runs on: the browser.
Componyx takes a different approach. The platform is already there. The browser already understands HTML, CSS and JavaScript. Componyx.UI and Bindary are built to work with those things, not replace them with a proprietary application structure or another layer of complexity you have to adopt. After more than a decade of development and real-world use, Componyx has become something I believe is worth sharing. Not because every project should be built this way, but because developers should have the option.