DEV Community

Eissa Saber
Eissa Saber

Posted on Edited on

A Quick Guide to OlumJS

I just published a quick guide to OlumJS covering the core concepts in 8 simple steps — from reactive state and props to slots, lifecycle, control flow, loops, and shared state.

OlumJS is built around a simple idea: keep writing HTML and JavaScript, while adding reactivity on top.

If you're curious about this approach, check out the guide:

👉 https://www.olumjs.top/blog/olum-quick-guide

Top comments (1)

Collapse
 
erlanggasatriasource profile image
Erlangga Satria •

wow its good to hear you build up reactiv js. Your engine use popular framework logic, component based. I also built engine 3.7kb gzip or 10kb minified, why tiny? coz using web api only and pure javascript. I tried built engine with different Dev Experience, its always html with binding, then javascript still javascript minimum directive and state can call across module, :for loop are component so maybe when we write product card just

<div class="product" :for="product in products">, my goal designer make beaute UI and feel custumer as UX mabye using css, animation or js, and backend engire just binding it. try benchmark, on low end android phone below $80 just 100-150ms in huge market country user using low-midle end phone, laptop just 50ms, how about your device? just tell me after you tried

Collapse
 
eissapk profile image
Eissa Saber • • Edited

thanks, olumjs is based on runtime + compiler
so you can write normal html file and get under the hood something like your syntax
mine is not flexible to get it mounted on other spa frameworks like react/vue since it needs a compiler
anyway i made mine to code my side projects in vanilla and get the same spa experince without bothering my self with docs and learning curve

regarding your library it's decent and minimal and flexible since it depends on runtime only so you can think about hooking it with other frameworks in the same application, that's a good feature that i can't do with mine (olumjs)