Modularization is a great idea

Back in the old days where there were no concept regarding frontend package management, we would lay out all the scripts in order in the html file, and hope for the best that they would somehow work together if order were right. This surely doesn’t work well with huge projects, but luckily back then JavaScripts weren’t so shiny anyways - UIs weren’t so cool and logic was much simpler. However, things do evolve. People soon noticed that this approach wouldn’t scale - cooperation across multiple teams becomes super tricky, if not impossible, and it doesn’t play well with DRY either.

Then people came up with a great idea of modularizing JS code (probably back in 2003?) the same way you would do for your beloved Java/C++ code libraries. And then there came the CommonJS definition concept by Kevin Dangoor back in 2009. Many people got to know this idea thanks to Node.js, and it works quite well, especially for server side code. Now you can easily use npm and build both the frontend and backend using the same tool very quickly, thanks to the JS community. Since people have the same interface for code modularization, team cooperation becomes much easier and projects gain benefit from much better encapsulation.

There are use cases where data need to be read from source to a sink without modification. In code this might look quite simple: for example in Java, you may read data from one InputStream chunk by chunk into a small buffer (typically 8KB), and feed them into the OutputStream, or even better, you could create a PipedInputStream, which is basically just a util that maintains that buffer for you. However, if low latency is crucial to your software, this might be quite expensive from the OS perspective and I shall explain.

What happens under the hood

Well, here’s what happens when the above code is used:

1. JVM sends read() syscall.
2. OS context switches to kernel mode and reads data into the input socket buffer.
3. OS kernel then copies data into user buffer, and context switches back to user mode. read() returns.
4. JVM processes code logic and sends write() syscall.
5. OS context switches to kernel mode and copies data from user buffer to output socket buffer.
6. OS returns to user mode and logic in JVM continues.

You should read this if

• You want to set up a personal blog
• You know what Markdown is
• You don’t want to set up a heavy Wordpress environment
• You don’t want to set up any database just for the blog
• You either don’t have a VPS or want to host blog content in some easy-to-reach place.
• You still want a template/theme system.

Solution

Github Pages + Hexo (what this site uses)