8 votes

Topic deleted by author

2 comments

  1. The_Fad
    Link
    I'm getting my wife a new car! Her current one is over 20 years old with hella miles, and this will be the first car she's ever bought from a dealership. It's still used, but it's MUCH nicer and...

    I'm getting my wife a new car! Her current one is over 20 years old with hella miles, and this will be the first car she's ever bought from a dealership. It's still used, but it's MUCH nicer and much more up-to-date functionality-wise than her current vehicle, or even mine which is an '08. She's super pumped and it's been fun for me because I've gotten to answer her questions re: buying from a dealership rather than through private sale.

    5 votes
  2. [2]
    Comment deleted by author
    Link
    1. unknown user
      Link Parent
      Writing a custom SSG that noone else will use is rather easy: I made one once with horrible Elisp hacks that produced a blog from an Org mode file; then later one that was an even horrible mess...

      Writing a custom SSG that noone else will use is rather easy: I made one once with horrible Elisp hacks that produced a blog from an Org mode file; then later one that was an even horrible mess using make, gawk, gm4 and maybe some Perl even; and currently I'm using a Ruby one that is less horrible but rather bare bones. But when API design and features you don't want comes into play, it becomes harder. I recently tried my hand at it, designing a Python class library for a flexible system, but I did not like the API I ended up with: it was bulky and messy. I do want to go back and start over with a functional API similar to Hakyll (or even just use it), but IDK if I ever will. It is a fun little type of pet project tho, which is also immediately useful to you once you get it done.

      2 votes