HIGHLY EXPERIMENTAL
FRDP is a tiny, reactive frontend framework (yes, yet another one!) designed for building small applications.
- Component system based on web components.
- Reactive all the way.
- State is optional.
- Purely Functional.
- No build required.
- Clear separation of HTML, CSS & JavaScript code. (Yes, I’m old-school.)
- Framework-level preferences.
- Signal library agnostic.
FRDP is intended to be minimalistic and closely aligned with core web technologies like Web Components, HTML, and JavaScript. Unlike other frameworks that introduce abstractions (such as virtual DOMs, component state management, or compilation steps), FRDP:
- Avoids unnecessary abstractions by working directly with native browser APIs.
- Does not require explicit state management. Reactivity is handled using derived signals, meaning state changes are automatically managed by signals, reducing the need for manual state management.
- No build step is required, making it simple to use right out of the box for small applications, without complex tooling.
You cannot create new signals manually. All signals must be derived from user events (clicks, input changes, etc.), server events, or time-based events.
No. FRDP is designed for smaller applications, focusing on simplicity and minimal overhead. For larger projects, established frameworks such as React, Angular, and Vue offer more comprehensive tooling, performance optimization, and ecosystem support.
FRDP does not enforce a specific state management system. You can integrate your own reactive signal library, like RxJS, Preact Signals, or any other reactive system of your choice.
TypeScript support is coming soon.
Component communication is managed by passing signals between parent and child components. This is akin to props and callbacks in frameworks like React and Solid, but everything in FRDP is a signal.
Nothing.
I am the machine and God is it's operator. - Sri Ramakrishna