{"id":338,"date":"2016-10-25T15:39:34","date_gmt":"2016-10-25T07:39:34","guid":{"rendered":"http:\/\/finaldie.com\/blog\/?p=338"},"modified":"2017-08-07T18:21:25","modified_gmt":"2017-08-08T01:21:25","slug":"boom-skull-engine-released","status":"publish","type":"post","link":"https:\/\/finaldie.com\/blog\/boom-skull-engine-released\/","title":{"rendered":"Boom! Skull-Engine Released"},"content":{"rendered":"

\"Skull\"<\/a>
\nI’m so excited to announce that the Skull-Engine<\/a><\/em><\/strong> is released today! Follow me to see the details.<\/p>\n

What’s Skull<\/em><\/h2>\n

Skull<\/em> is a serving framework, it can start fast, has high development productivity and is easy to maintain.<\/p>\n

Why was Skull<\/em> born?<\/h2>\n

To start a new project, we usually need to read tons of documentations of the chosen framework\/tech stack, then decide whether to use it and how to use it. It may take a week or more for a newbie, even for an expert, it sometimes still needs a batch of trivial efforts to build it from a scratch. It’s really a terrible experience for us. Life is short, let’s save the time on the most important things instead.<\/p>\n

After we have a project, we will need to modify the code\/configuration again and again, and do the test, sometimes we really want to switch to another language to solve a specific problem, but it’s extremely hard to do that since we’ve already chosen a programing language for the project at the beginning. Have you ever regretted for the decision? For example, C\/C++<\/em> provides high runtime performance, but the development cycle is very long, people should be really careful to deal with the low-level memory issues; On another hand, Python<\/em> has rich packages to solve the problems, but the performance is much worse than C\/C++<\/em>, could we use them all in one program, to choose the right language in the right place, and the different language can communicate with each other very easily and smoothly?<\/p>\n

Besides, it’s hard for people to understand the complex program, especially when the code become more complex and huge, it’s just like a big black box, and no one knows how it works, it would become un-maintainable since no one can see it clearly, even a basic workflow. Imagine that, how could a programmer figure out the basic workflow of a complex program without documentation in 5 minutes?<\/p>\n

Under this situation, Skull<\/em> was born to solve those kinds of problems.<\/p>\n

<\/p>\n

Key Components and Features<\/h2>\n

Skull<\/em> is based on Google Protobuf<\/a> and Flibs<\/a>, target to Linux<\/em> platform. It’s consist of 3 components:<\/p>\n