Earlier quoted context omitted.
cat header > index.html cat page >> index.html cat footer >> index.html
cat header page footer > index.html ("cat" is short for "concatenate".) ;)
even better! (although you may want some steps in between)
The ideal tech stack for a personal developer blog in 2020
271–275 of 275 posts
Re: The ideal tech stack for a personal developer blog in 2020
#272Earlier quoted context omitted.
In what way do you think HTTP is out of control? Before you reply please keep in mind JavaScript web apps don't have anything to do with HTTP.
Ok, "out of control" is a slight exaggeration, but HTTP has become a complete reimplementation of what amounts to TCP or SCTP.
Again, in what way? TCP is making sure data gets where it's going and there were no errors introduced by the transmission. A raw TCP socket doesn't have any metadata about what the data is that's coming over the socket. There's a reason the Application layer exists in the first place.
You can make an argument that HTTP should be replaced with another application later protocol but just raw sockets everywhere is ridiculous.
HTTP has eaten the world of application layer protocols because it is flexible and expressive. It's also relatively easy to implement and there's lots of good FOSS server packages available. Most servers make it really easy to plug in back end applications. Combine that with ubiquitous HTTP clients and it's a super low barrier to entry.
You're not going to replace that ecosystem easily and you definitely won't replace it with raw sockets.
Re: The ideal tech stack for a personal developer blog in 2020
#273Another aspect is that your blog should make you want to blog. The tech stack therefore mirrors your interests. It feels great to use tools built by _yourself_ for _yourself_. Doubly so if the stack is janky (rust / org-mode for me). The feeling that you've made something makes you want to invest more into it. To make sure the tools were worth making in the first place.
Oh god, don't tell me about janky stack. My stack for the blog is Org Mode compiled by Emacs into HTML, which then gets parsed by my Common Lisp static site generator. It's a weird setup, but it came to be because: - The rest of the site, and the overall template, is generated straight from Common Lisp (using a much saner syntax for markup and styling than HTML/CSS), - writing a parser for Org Mode for anything but t…
That's indeed a janky setup :P
What libraries / frameworks do you use in Common Lisp to generate the site?
Re: The ideal tech stack for a personal developer blog in 2020
#274Earlier quoted context omitted.
Oh god, don't tell me about janky stack. My stack for the blog is Org Mode compiled by Emacs into HTML, which then gets parsed by my Common Lisp static site generator. It's a weird setup, but it came to be because: - The rest of the site, and the overall template, is generated straight from Common Lisp (using a much saner syntax for markup and styling than HTML/CSS), - writing a parser for Org Mode for anything but t…
That's indeed a janky setup :P What libraries / frameworks do you use in Common Lisp to generate the site?
CL-WHO - to generate HTML
LASS - to generate CSS
colorize - to colorize source code snippets and embed documentation links in them
Plump, Plump-SEXP, CLSS - for occasional fixing of imported HTML documents "on the fly"