fiberjs/fiber-framework

The natural way of building JavaScript Applications

#Fiber

The framework is in prototype stage and is under active development. Breaking changes are going to be introduced until first beta release is out.

Some example applications were written already with many tweaks in the system. There are still many open questions, but hopefully soon it can move to beta stage after performance testing proves it is production ready and can handle the load of larger applications.

Demo apps:

• Github repo browser
• blackJack game
• TodoMVC
• performance tests with TodoMVC

The vision

We want a way to build JavaScript Apps without magic and Bible sized documentation.

We want to use and understand web technologies like HTML5, CSS3 and JavaScript.

We want to be in charge of design decisions regarding state encapsulation, rendering, performance.

#Fiber Should be

• simple
• reliable
• flexible
• debuggable

#Fiber Should NOT

• have magic
• grow to the size of the Eiffel tower
• come with extensive boilerplate
• be opinionated

Features

• event-driven architecture
• decoupled components
• super lightweight
• non-opinionated
• easily debuggable and testable
• smooth like a well done cappuccino ☕

Following the footsteps of FlightJS

Using the orininal drive behind FlightJS: to help you write highly scalable and maintainable code as a strong base for your applications. Fiber's event driven architecture will help you to avoid design mistakes like tight coupling or dependency-hell - when you have to scroll a page of dependency imports to see your code and you have to refactor all your tests because you changed something in a service.

But enhanced

• Less freetext events, more stability
• immutable event data
• Using ES6, Webpack and modern debugging tools
• Features state encapsulation in namespaces, but you can use it with Redux or can write stateful components - the choice is yours to make.

Using a custom pub/sub system to host data events makes communication faster and more reliable. By declaring clear namespaces for certain resources and their events, and joining them with an isolated state we can create a system that is easy to read, understand and maintain.

Most frameworks are wasting lots of resources on dependency injection when the best way to tackle dependencies is to get rid of them as much as possible.

Another typical problem of modern frameworks is that they are trying to be the swiss-army-knife of all your problems - becoming too complex and restrictive in the process.

Fiber is designed to be modular. Its core is kept small, simple and extendable.

What's next?

• (done) webpack built minified version ( index.js )
• (done) performance test
• finalizing namespace and basic API
• writing tests to ensure stable state after first prototype stage is over