4 ms·
Three issues with it: 1. Installation instructions are to use npm. I already have a package manager and don't intend to learn a new one for every language. 2.
by flukus 9y ago
Three issues with it:
1. Installation instructions are to use npm. I already have a package manager and don't intend to learn a new one for every language.
2. Javascript/npm based. I refuse to install that monstrosity on my system ever again. I don't know how much memory it uses, but I'm willing to bet it's a lot more than existing IRC programs.
3. What's with the server? Why not standard IRC?
- aichholzer 9y agoI had to laugh at your second point; "monstrosity", that was really creative. Actually, it does not use too much memory, given what it is, a JS application, that runs virtually within something else, there are no two ways about it. JS was the language of choice simply because of the easiness of getting the product out there. If I was to write this in plain C++, even Go or Rust, memory usage would be less, but that's not in my near future plans. As for the server; I wanted fully to use websockets and I wanted to keep it simple. IRC would mean another layer which I is not part of my scope here.