Currently in beta stage, but it is used already in couple projects, such as one of my client’s internal android mobile app or as a SPA framework for inku.js interface.
Rakun.js is developed with zero-dependency approach and can be used with existing tools, e.g. axios or jQuery plugins.
Nowadays developers tend to complain about rapid development of popular tools and approaches of using them.
I was one of them.
But I decided to free ourself from this trend by creating Rakun.js.
I’m into web development since I’ve learned about what is HTML and when using
<table><table> was the only right approach of creating websites.
Then SPA happened.
But tools that were meant to just support web development wanted to be more and more universal, which led to their overcomplication. Task runners which were at first an optional helpers for repetitive tasks has transformed into necessary components of SPAs. There’s even a meme about random programmer who - after spending a whole weekend configuring webpack - is finally ready to start programming his side project.
We have new abstraction layers, such as Virtual DOM (and I’m waiting for another abstraction layer for it - we need to go deeper trolololo :D ) - but don’t get me wrong - it’s a good thing that people are making new, awesome tools, but most of programmers just follow the hype and use them everywhere they can (even they shouldn’t).
Personally, I was really tired/frustrated/You-name-it of constantly keeping up to date with another shiny react-like-but-smaller/better/more-awesome lib (which I even haven’t like to work with in the first place).
I had a constant feeling that I’m not up-to-date with my technologic field of expertise.
In the following Rakun.js devlogs I’ll present the way how it works and share some basic usage tips.
And how’s about You? Do You follow the hype or prefer to work classy?