4. Efficiency or Speed
Prev | Chapter 10. Plugins | Next

## 4. Efficiency or Speed

eJourn's plugin system is very efficient. A well written plugin should not cause any noticeable loss in speed for a few reasons.

1.) eJourn only allows plugins written in c.

Since eJourn's plugins can only be written in the same language as eJourn you don't have to wonder if a plugin is slow because of its language.

2.) eJourn plugins have no cost for things they don't do.

Since eJourn's plugin system basically just calls certain methods in plugins every time they're needed (for example, it tells all plugins when it's saving), and the plugins have the option of supporting these calls: The only time a plugin will use any time is when it supports a call. So, if a plugin doesn't need to do anything when you save, it won't. So having 200 plugins shouldn't be a big deal. However, there is a small startup cost at program startup to make it cheap to call them later; but this is very small.

3.) I've written them all

Ok, so that sounds egotistical. But the point is that the quality of the plugins should be similar to the quality of the whole program since they share the same author.

Other people are always welcome to write plugins and I encourage it (sometimes actively). However, before I include them I certainly will look them over hard.

Prev | Up | Next
3. Why Plugins? | Home | Chapter 11. Filing Bugs