| Why do we need another framework for Node.js?
This is my wish list: I want to build my web application on a framework with zero dependencies. I want to utilize native Node.js APIs without any additional layers of abstractions. I want to hack my framework when I need to, e.i. I want to have quick access to my framework's folder and make quick changes. I want to have zero downtime when I update my appliction's logic just by sending a signal. I want to use Cluster in Node.js. It will allow me to scale my application with very little price. I also don't want to anything else for orchestration and other fancy things that Node.js provdes itlself. I want to have HTTP/2 as a default. I want to handle 500 User error properly. I want to configure my application out of box in my primary and worker processes. I want to have very simple secrets reader. I want to be able to log into an output log file. I want to have composable API provided by my framework and not use middlewares that reduces the code clarity. I want to be able to copy/paste logic to achieve clarity. I want to have access to params and queries in each request URL. I want to have control when I read body of my requests. I want to have quick access to my external dependecies like db clients and other integrations without attaching them to request object. I want to have dependecy injection without any huge frameworks. I want to easily configure my index.html, not-found.html files. I want to focus on building my products quicky and make money. Hopefully it can be interesting for somebody who want something similar from a framework. |