Cycle.js – A functional and reactive JavaScript framework for predictable code
I am definitely an advocate for reactive programming, as I have used React Native to develop a cross-platform mobile application (<a href="https:&#x2F;&#x2F;dedicate.datasilk.io" rel="nofollow">https:&#x2F;&#x2F;dedicate.datasilk.io</a>), but when it comes to web development, I am very much an advocate for using the basic tools that were given to us web developers to build web applications.<p>These tools include mainly HTML &amp; CSS, and when needed, &quot;vanilla&quot; JavaScript (and maybe even a compact jQuery alternative like zepto), but in no way do I advocate for using client-side frameworks for developing web applications. It is because they are difficult to debug, sometimes near impossible, and also because it leads the developer astray from practicing basic concepts such as writing beautifully formatted HTML &amp; CSS or utilizing small bits of JavaScript for event handling &amp; AJAX calls. Instead, they are forced to focus nearly all of their attention to writing JavaScript in what I call a &quot;black box&quot; environment where they send input into the black box and the magical sorcery of said black box somehow outputs a graphical user interface.<p>A web application should harness the power of the web browser&#x27;s native capabilities instead of harnessing the powers of a JavaScript framework, because the web is a beautiful place made of beautiful technologies that were built in the golden era of technological creativity. Because of such creativity, many great people came together and invented HTML, CSS, and JavaScript, the near-perfect solution to a very complex, graphically interactive problem.<p>Sure, you may think that you want to build a single-page application, and that&#x27;s fine. Why not test your skills and write a micro-library that harnesses the HTML5 History API along with a simple AJAX method to transform your website into that single-page app you fantasize about daily.<p>Sure, you may think using the JavaScript &quot;import&quot; keyword in all of your many JavaScript files is okay because it&#x27;s a single-page app that you&#x27;re building and all those thirty-some-odd JS files will only be loaded one time for each user session when the app initializes, but what you don&#x27;t understand is that you are lazy and careless and on a daily basis, you make excuses for all of your sins.<p>You and I both know that your application only needs ONE small JS file on initialization and ONE dynamically loaded JS file for each area within the app that your user may or may not navigate to in the first place.<p>So, for the love of all humanity, please, please, write HTML &amp; CSS, and pepper it ever-so-lightly with bits of JavaScript (but only when it is absolutely necessary).<p>If you need a more convincing argument to steer away from client-side JavaScript frameworks, simply read this small comic strip: <a href="https:&#x2F;&#x2F;xkcd.com&#x2F;927&#x2F;" rel="nofollow">https:&#x2F;&#x2F;xkcd.com&#x2F;927&#x2F;</a>