Code Reggae

What for? 

The blog is intended for using rust programming language for liberating code ideas that sometimes disturb my sleep. Rust is an "ML in the C skin" language, it is a system-level language allowing for writing an operating system on bare metal (see Redox), increased reliability (due to ownership model), rich libraries set, great build system and without the garbage collection. The main idea is to rewrite a well-known piece(s) of software on rust and correct the shortcomings by using the rust unique language properties.

Correct what?

The main idea is to use rusts ownership model for detection and correction of shared variable usage. Often such usage is scattered throughout the code tree of old and respected C projects and prevents to switch to modern concurrency model. For example, PostgreSQL starts a process (!) per client instead of utilizing threads or co-routines. Data between those processes is shared using OS-level shared memory. That's ugly and against the will of Jah! If PostgreSQL will be rewritten in idiomatic rust there would not be a problem to switch the concurrency model and thus improve the performance.

How?

Surely enough - one may do it the hard way - manually. But that is not the reggae style. I aim to use the c2rust transpiler and refactoring tools to perform that task.

Enough for the first post - philosophical approach is stated, let's see what I can do (if anything).   

Comments

Post a Comment

Popular posts from this blog

Oberon: what is it good for?

The first version of Oberon was created at the end of 80-ies and the beginning of 90-ies. Niklaus Wirth was back then a well-known and influential figure in Computer Science. His work was open source, well described, and available for download. But time went by and the system did not leave the academic world and his university. Even the German-speaking world seems not to pick it up. So, why? And why should we even pay an attention to this system? First of all, what is Oberon and what is its goal? It was created as an illustration for the Operating Systems course and exercise in building an operating system that can be fully understood by a good student. The whole system was built originally by one man from scratch. So, it is fantastically compact. It allows for extension, and simultaneously it also allows for the reduction of all the code that is not currently used. It is amazingly reliable. It is lightning fast. But it is not widely used and not even widely known. It seems to have its
Read more

Active Oberon is still alive

 After the previous post, I was looking at Oberon-related stuff. Seems that a couple of ideas are still alive - Active Oberon, both operating system and language.  There is an unofficial GitHub mirror of the  Active Oberon working group. Active Oberon team still uses svn, so the unofficial mirror is updated only from time to time. The Github mirror has several builds - I tried the linux64, and everything seems to work just fine.  I even found there an ARM version of the compiler and Active Oberon for an ARM-based board . And this is extremely interesting - because this world does not have a good real-time OS for "embedded" programming. If Oberon can be used for this purpose - it can be a  success. But in order to be successful, someone should port several utilities (well - the simplest version of shell and sshd comes to mind first) and, probably, several C libraries to A2OS (as they call the Active Oberon OS now).  It seems to be really ready for cross-compiling. So, in the
Read more