## Introduction
Pacem JS is an ecosystem of reusable web components, built on the browser's own [Custom Elements](https://html.spec.whatwg.org/multipage/custom-elements.html).
It follows the **MVVM** pattern, with a binding syntax of its own, and it's written in [TypeScript](https://www.typescriptlang.org).
There's no root component and no bootstrap call: drop the elements into any page and they bind themselves, on the fly.
This is a complete, working piece of Pacem JS:
```html
<pacem-data id="profile" model="{ name: 'Ada' }"></pacem-data>
<pacem-input-text value="{{ #profile.model.name, twoway }}"></pacem-input-text>
<pacem-text text="{{ 'Hello, ' + #profile.model.name }}"></pacem-text>
```
### At a glance
{{ }} attributes (one-way, two-way or once), on-* handlers<script> tags or ES modules, bundler optional## Why another JS framework? Many reasons. First of all, I ([Cristian Merighi](https://pacem.it/blogs/polyhedric)) have no more time to spend switching from one technology trend to another, then to yet another, and so on and so forth... That's what happened to *me vs JavaScript frameworks* over the years. Definitely out of **jQuery**, and having learned to love the **MVVM pattern** years before (with **WPF** and **Silverlight**), I stumbled upon **[KnockoutJS](https://knockoutjs.com)**: it was good, and I built a piece of my client-side "world" on top of it. Then came **[AngularJS](https://angularjs.org)**, which was better: I rebuilt my previous world, plus many others, on top of it. Then came **[Angular](https://angular.dev)** (2+), even better, and cool for having **TypeScript** as its default language: I rebuilt my whole universe on top of it (one whole month to learn it and migrate the code). > That was it! Besides, I (always me) couldn't find anything that fitted my *desiderata*: - **no dependency bloat**: Pacem JS has zero runtime dependencies; - **no imperative bootstrapping**: it had to start by itself; - **close to the platform**: respectful of the browsers' standards and of their native capabilities, custom elements first. *Experimenting* was another big push, and [TypeScript](https://www.typescriptlang.org) made the decision to start an easy one. ## What it is, what it isn't **Pacem JS** is meant for **internal use** at [Pacem](https://pacem.it), in web and cross-platform apps alike. It targets modern, evergreen browsers: no legacy ones, no polyfills. > **Pacem JS** doesn't want to be adopted: it aims to demonstrate that you can build your own. Born as a prototype, it has grown into a broad toolbox: forms and scaffolding, charts, maps, 2D and 3D, a theme engine. It isn't perfect, but it's worth playing with. This documentation site is itself a **SPA** (and **PWA**) built with **Pacem JS**.
To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behavior or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.