Earlier quoted context omitted.
The way you phrased this makes it seem like you aren't a programmer and are looking in from outside of the programming world. On another note: a less condescending way of conveying the same message would have been "Cool project. Pokésay would have been a great name instead of Pokemonsay."
I... am a programmer. And I'm terrible at naming too, usually. It was just a light-hearted comment.
Pokemonsay: Pokemon Version of Cowsay
31–40 of 54 posts
Re: Pokemonsay: Pokemon Version of Cowsay
#32Imagine installing node.js and a json parser and 10+ other things just for a cowsay clone. I can't imagine what a clean install of all this crap would be just for this project.
One person's complaint about a json parser being too heavyweight is just as valid as the complaints that the arcane one-off cow template syntax is hard to use and understand.
Not to mention that this has different features than cowsay, and it's just a fun little project. It parses image files into the terminal display, it can scrape 3rd party websites to download new Pokemon images.
Re: Pokemonsay: Pokemon Version of Cowsay
#33I'm curious how close to this you could get with regular cowfiles for cowsay.
Re: Pokemonsay: Pokemon Version of Cowsay
#34While it does support a few additional options according to the README, I think this whole project could have consisted of no code at all and just cowsay template files that you’d copy to the cowsay template directory. Typically /usr/share/cows/ Here is an example of a third-party template for cowsay: https://github.com/lochsh/alpacasay/blob/master/alpaca.cow
Re: Pokemonsay: Pokemon Version of Cowsay
#35I find it curious how programmers are so poor at naming their projects. This could've easily been named pokésay. That said, it's a cool project!
Re: Pokemonsay: Pokemon Version of Cowsay
#36I really like this module and love the idea. The images are far too big though especially compared to cowsay/cowthink.
This seems to just use blank spaces with terminal background color codes to draw things, which means your smallest "pixel" is the size of a terminal line.
Are there ways of getting higher definition in a terminal with fairly widespread support and keeping full color?
The hacker part of me is thinking with some combination of finding Unicode characters that "fit" an outline combined with color quantization (since every "character" has to be one color at most) might be able to cut the size in half...
Re: Pokemonsay: Pokemon Version of Cowsay
#37While it does support a few additional options according to the README, I think this whole project could have consisted of no code at all and just cowsay template files that you’d copy to the cowsay template directory. Typically /usr/share/cows/ Here is an example of a third-party template for cowsay: https://github.com/lochsh/alpacasay/blob/master/alpaca.cow
The actual code used to pick a random Pokemon and display it is only a few dozen lines.
Re: Pokemonsay: Pokemon Version of Cowsay
#38I find it curious how programmers are so poor at naming their projects. This could've easily been named pokésay. That said, it's a cool project!
>This could've easily been named pokésay Not for users with a US keyboard
Re: Pokemonsay: Pokemon Version of Cowsay
#39Earlier quoted context omitted.
The way you phrased this makes it seem like you aren't a programmer and are looking in from outside of the programming world. On another note: a less condescending way of conveying the same message would have been "Cool project. Pokésay would have been a great name instead of Pokemonsay."
I... am a programmer. And I'm terrible at naming too, usually. It was just a light-hearted comment.
Re: Pokemonsay: Pokemon Version of Cowsay
#40I find it curious how programmers are so poor at naming their projects. This could've easily been named pokésay. That said, it's a cool project!