Moe-counter fork

I decided to fork the Moe-counter project and host it myself. It is publicly available at count.chiya.dev and anyone is free to use it.

The original Moe-counter instance at count.getloli.com seems to be very unreliable because it is hosted on a free repl.it plan. In comparison, my instance is hosted on a dedicated server running 24/7, so it should be more reliable.

Forking was necessary because the original project had hardcoded links and references to analytic scripts. The domain was changed to chiya.dev and analytic scripts were removed.

I intend to keep this fork up-to-date by merging upstream changes periodically.


Happy new year!

2021 came and went really quickly, and now it’s 2022. For me, lots of things happened but nothing too special. I suppose that’s a good thing?

That virus starting with ‘C’ really messed with people in 2020 and 2021. I was not as severely affected by it as were others, but it could have been worse. Let’s hope it fades away into history for good in 2022.

This year I plan on continuing to work on some open source projects in my free time. I also have some ambitious projects that are very slowly being materialized on my disk. If I ever complete them, I may publish them as open source.

Happy new year!


Why I wrote my own package manager

Check it out on GitHub.

I use Neovim as my IDE with plenty of plugins for various language integrations and editing tools, but configuring those plugins using existing package managers was always a pain.

Every time I copied my configuration to another development environment, the configuration script would spew a bunch of errors saying that packages were not installed. Obviously, duh. It’s a new environment.

But isn’t the point of a package manager to make managing packages easy and painless? If a package doesn’t exist, it should handle that case gracefully instead of filling my screen with errors I’m already aware of.

require("packer").startup(function()
  use("wbthomason/packer.nvim")
  use({
    "nvim-telescope/telescope.nvim",
    requires = {
      "nvim-lua/plenary.nvim",
      "nvim-treesitter/nvim-treesitter",
    },
    config = function()
      require("telescope").setup({
        -- omitted
      })
    end,
  })
end)

This is a portion of my old configuration file for the package telescope.nvim, using packer.nvim as the package manager.

If I copy this configuration to a new environment without any packages installed, I expect the package manager to handle the change correctly. That is, it should not run the config hook, because the package isn’t installed. There is nothing to configure.

Instead, when I ran :PackerSync in the new environment, what I got is a bunch of errors saying telescope.nvim failed to initialize.

packer.nvim: Error running config for telescope.nvim: [string "..."]:0: module 'telescope' not found:
^Ino field package.preload['telescope']
^Ino file './telescope.lua'
^Ino file '/usr/share/luajit-2.1.0-beta3/telescope.lua'
^Ino file '/usr/local/share/lua/5.1/telescope.lua'
^Ino file '/usr/local/share/lua/5.1/telescope/init.lua'
^Ino file '/usr/share/lua/5.1/telescope.lua'
^Ino file '/usr/share/lua/5.1/telescope/init.lua'
^Ino file '/home/phos/.cache/nvim/packer_hererocks/2.1.0-beta3/share/lua/5.1/telescope.lua'
^Ino file '/home/phos/.cache/nvim/packer_hererocks/2.1.0-beta3/share/lua/5.1/telescope/init.lua'
^Ino file '/home/phos/.cache/nvim/packer_hererocks/2.1.0-beta3/lib/luarocks/rocks-5.1/telescope.lua'
^Ino file '/home/phos/.cache/nvim/packer_hererocks/2.1.0-beta3/lib/luarocks/rocks-5.1/telescope/init.lua'
^Ino file './telescope.so'
^Ino file '/usr/local/lib/lua/5.1/telescope.so'
^Ino file '/usr/lib64/lua/5.1/telescope.so'
^Ino file '/usr/local/lib/lua/5.1/loadall.so'
Press ENTER or type command to continue

After many trial and error, I discovered that the fix to this problem is manually commenting out all hooks, letting packer download the packages first, then uncommenting everything. This became incredibly tedious very quickly.

Interestingly, this meant that packer did not meet the very definition of a package manager according to Wikipedia.

A package manager or package-management system is a collection of software tools that automates the process of installing, upgrading, configuring, and removing computer programs for a computer in a consistent manner.

Clearly, having to comment out hooks and scripts just to get a list of packages installed in a new environment is not an automated process.

Note that this problem is not unique to packer. I have encountered similar issues with paq-nvim.

Also, there were many other minor inconveniences with packer, such as having to compile my configuration separately, no access to global variables, the inability to disable packages temporarily, and having one giant package list that was becoming almost unmaintainable.

I decided I had enough and wrote my own package manager, naming it dep, with the aim of solving all of the above problems and more. With dep, I am finally happy knowing that I can restore my full neovim setup in under ten seconds by simply copying my configuration files.

This turned out to be really convenient, because right after having written dep, I had to uninstall my hackintosh and distro-hop between Arch and Fedora several times while upgrading my main disk. My package manager has not failed me yet.

Although I wrote dep out of a personal need for a reliable and correct package manager, I have released it under the permissive MIT License for anybody else interested to try out. The repository readme, although brief, should guide you around how you can use it effectively. As always, if you discover a bug or want to suggest a feature, please open an issue!

Link to GitHub


Switching to Jekyll

First post!

Today I updated chiya.dev to be completely static. It is now serving simple, plain HTML web pages generated using Jekyll.

Before this change, I was running a custom React website that presented a responsive landing page with some social links. It was unnecessarily slow and Javascript-heavy for a landing page.

Jekyll is customizable and has a wide range of themes, so it was an easy choice for a quick and simple website like this one. This website is running a slightly customized Hyde theme. Plus, built-in support for blogging is pretty nice.

Now that I have a blog, I will occasionally post here if I feel like writing stuff.