4 ms·

This is a neat idea, but I wish it would respect some basic Unix standards by default. Two big annoyances jump out at first glance: it assumes you want to use p

This is a neat idea, but I wish it would respect some basic Unix standards by default. Two big annoyances jump out at first glance: it assumes you want to use port 22120, and it puts its config in ~/22120-arc. Maybe both of these are configurable, but the directory is a terrible default. Use XDG (~/.config/22120) or at least use a hidden directory in the home dir. And the port it operates on should be completely configurable. Naming the project 22120 is a terrible idea, and assuming that port won't need to change is bad practice. I'm not making any value judgment about the actual tool. It sounds interesting enough. But it should behave better.

fizixer 6y ago
I agree what you say while also pointing out that unix home directory has become a complete mess. Anyone (any installed software) can do whatever they like, there is no mechanism of enforcement, and advice in the form of constructive critque or comment is not even a drop in the bucket towards fixing the problem.
- noitpmeder 6y ago
  I find that I want to use a project _more_ if they follow best practices like using ~/.config/{app_name}. Attention to details like that usually indicate a higher quality piece of software overall.
neolog 6y ago
> Use XDG (~/.config/22120) That's only for configuration files. The actual data should go in $XDG_DATA_HOME, by default ~/.local/share/22120/. Many languages have a tool (e.g. https://pypi.org/p/appdirs/ https://pypi.org/p/appdirs/ ) for finding the appropriate data/config/cache directory for each OS. https://wiki.archlinux.org/index.php/XDG_Base_Directory https://wiki.archlinux.org/index.php/XDG_Base_Directory
graderjs 6y ago
Hey, I feel really sorry for you that you did not have a good or accurate experience of this. It must seem like it does not respect your wishes, or would not if your tried it more. Okay so... The config is actually located in hidden file, here: https://github.com/c9fe/22120/blob/8b6cc758f14d34f564fd3a8383c0683501895603/args.js#L10 https://github.com/c9fe/22120/blob/8b6cc758f14d34f564fd3a838... const pref_file = path.resolve(os.homedir(), '.22120.config.json'); And the port is fully configurable here https://github.com/c9fe/22120/blob/8b6cc758f14d34f564fd3a8383c0683501895603/args.js#L5 https://github.com/c9fe/22120/blob/8b6cc758f14d34f564fd3a838... const server_port = process.env.PORT || process.argv[2] || 22120; I don't agree with you about the name. And I get if you're saying you feel the name should not be linked to a port number, but i also don't agree. I guess i can explain my thinking, but I'm not sure if they will help you understand or like it. Basically I like the name and I did consider changing it a few times but it just stuck for a number of reasons. And I can't remember exactly now but the port number might have come after the name. I think it's a good idea and cool if you have the server running on the same board that the name is but at the same time I know you might have something else running on that port so that's why I made it configurable. I guess she might also want to run more than one copy... But I'm pretty sure that we can't open two chrome windows with different debugging ports using the same user data directory. Anyway, that might be more info than you want or care for, and it might not help, but hopefully you have a clearer picture at least. I get if you still don't like it, but i just feel sorry for you that you didn't have a good experience of this. I did not design it to annoy you.

fizixer 6y ago

I agree what you say while also pointing out that unix home directory has become a complete mess. Anyone (any installed software) can do whatever they like, there is no mechanism of enforcement, and advice in the form of constructive critque or comment is not even a drop in the bucket towards fixing the problem.

noitpmeder 6y ago
I find that I want to use a project _more_ if they follow best practices like using ~/.config/{app_name}. Attention to details like that usually indicate a higher quality piece of software overall.

neolog 6y ago

> Use XDG (~/.config/22120) That's only for configuration files. The actual data should go in $XDG_DATA_HOME, by default ~/.local/share/22120/. Many languages have a tool (e.g. https://pypi.org/p/appdirs/ https://pypi.org/p/appdirs/ ) for finding the appropriate data/config/cache directory for each OS. https://wiki.archlinux.org/index.php/XDG_Base_Directory https://wiki.archlinux.org/index.php/XDG_Base_Directory

graderjs 6y ago

Hey, I feel really sorry for you that you did not have a good or accurate experience of this. It must seem like it does not respect your wishes, or would not if your tried it more. Okay so... The config is actually located in hidden file, here: https://github.com/c9fe/22120/blob/8b6cc758f14d34f564fd3a8383c0683501895603/args.js#L10 https://github.com/c9fe/22120/blob/8b6cc758f14d34f564fd3a838... const pref_file = path.resolve(os.homedir(), '.22120.config.json'); And the port is fully configurable here https://github.com/c9fe/22120/blob/8b6cc758f14d34f564fd3a8383c0683501895603/args.js#L5 https://github.com/c9fe/22120/blob/8b6cc758f14d34f564fd3a838... const server_port = process.env.PORT || process.argv[2] || 22120; I don't agree with you about the name. And I get if you're saying you feel the name should not be linked to a port number, but i also don't agree. I guess i can explain my thinking, but I'm not sure if they will help you understand or like it. Basically I like the name and I did consider changing it a few times but it just stuck for a number of reasons. And I can't remember exactly now but the port number might have come after the name. I think it's a good idea and cool if you have the server running on the same board that the name is but at the same time I know you might have something else running on that port so that's why I made it configurable. I guess she might also want to run more than one copy... But I'm pretty sure that we can't open two chrome windows with different debugging ports using the same user data directory. Anyway, that might be more info than you want or care for, and it might not help, but hopefully you have a clearer picture at least. I get if you still don't like it, but i just feel sorry for you that you didn't have a good experience of this. I did not design it to annoy you.