browser-base

After implementing my new browser home page (browser-home) and then discovering that my browser no longer supports loading such a page from the filesystem (see browser-home (Part 2)), I put a lot of thought in how to proceed. I made some decisions during a hike today.

All of the options would benefit from management software, so I will move in that direction. Writing that software is not my current priority, but I will put the project on the back burner and see how it goes. The first version will be minimal, so it should not take long to develop.

Deciding on a name for the project, however, is difficult! The version that I developed many years ago was called BrowserBase. (I used CamelCase for project names at the time.) When implementing the new version earlier this week, I called it browser-home (a literal description of the usage) because I have another project called base. Such a name is sufficient for configuration on my personal computer, but I should probably pick a better name for the management software.

I thought of many possible names, but all of them are already taken by other projects. I do not want to spend more time picking a name than programming, so I decided to use the old name in kebab-case: browser-base. Searching for other uses of the name, I found one hit: a GitHub repository named wexond/browser-base. It is the base (core) implementation of a browser called Wexond; the software itself is not called browser-base.

I am not changing the previous two blog entries, as browser-home is the name of the hand-coded prototype that I worked on this week. I am updating the tag to project:browser-base, however. Checking my server logs for RSS hits, it does not look like the change will inconvenience anybody.