Crucible – The Future
So these last few days I have been working more on this project. I can actually say it brings me great joy to do this project. It is the combination of tight restrictions that allows my creativity to flow and see just how far we can take this concept and library.
Cache
I want to implement a caching mechanism for both in-memory and file based cache. The in-memory will just be an associative array with some functionalities in there. The file based one will have the associative array be declared and written to a temp file. It will feature timer based expiry component that checks if it should be evicted. Auto fetching a cache maybe, if it is used when consuming an API.
This all can be built on top of the just completed maps
module.
Classes
I want to make a module for classes. They will not really be classes but sort of declared variables and a list of class definitions and class instances. However I think it will be quite fun and funny to see this in action. It will also contain a method called ctor
which will instantiate things, then you can always just put down:
class_instance.a=1
Like in Python and now it will have that property.
HTTP framework
It would be fun to make a http
module that will be able to make requests. It would make get requests with wget
maybe but actually send POST requests with the use of nc
.
Web framework
To take it a little further what I want to try and make is a Unix domain socket and have it hook into a live running Bash process that will read it and execute controllers based on the routes. It should make use of the processes
, io
, http
and class
modules.