111–120 of 275 posts
Another 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.
Everything is quite outdated, mind.
Authors first requirement is “I want to build the site in React and TypeScript. I love them both wholeheartedly, I use them for my day job, and they're gonna be around for a long time. Plus writing untyped JS makes me feel dirty.” That preference is not true for others and I feel like that makes the article’s title misleading.
how many months does that translate to in frontend dev time?
> Devii is powered by Next.js. We chose Next.js because it's the simplest, most elegant way to generate a static version of a React-based website. There's nothing simple about this crapton of dependencies. Sure, it may be easy to build things this way, but let's not conflate the two terms.
The other day I started an HTML document from scratch, in VSCode. I kinda blacked out and came to 5 seconds later, and thanks to autocomplete and muscle memory, the whole skeleton of a document was there. HTML and Head and title and body and all that. It was so fast & fluid. I'm ashamed to say I'd kinda forgotten how easy it is to just write fucking HTML . It's even got me reconsidering things like Markdown—I mean, f…
Edit: Bonus! I did the same for my brothers website: https://schnittfest.gmbh/ Just if you're curious.
The other day I started an HTML document from scratch, in VSCode. I kinda blacked out and came to 5 seconds later, and thanks to autocomplete and muscle memory, the whole skeleton of a document was there. HTML and Head and title and body and all that. It was so fast & fluid. I'm ashamed to say I'd kinda forgotten how easy it is to just write fucking HTML . It's even got me reconsidering things like Markdown—I mean, f…
Authors first requirement is “I want to build the site in React and TypeScript. I love them both wholeheartedly, I use them for my day job, and they're gonna be around for a long time. Plus writing untyped JS makes me feel dirty.” That preference is not true for others and I feel like that makes the article’s title misleading.
>they're gonna be around for a long time how many months does that translate to in frontend dev time?
Typescript is here to stay. No question.
React has been a thing now for what, six years? And it feels like 80% of FE job opening require React. And no major shift on the horizon.
Here's my stack: I write .html files in GNU Nano, and serve them with Apache. I've done that for about 20 years (with varying editors and servers), and I don't see why it needs to be any more complicated putting words on the internet. Yes yes, old man yells at cloud etc, but I'm a strong believer in "less is more".
It becomes more complicated as soon as a you have a sidebar with "Last articles" in which case you would need to edit each single HTML files to edit the sidebar consistently. Even with a single archives page you need to think about updating the archive for each new article. Also Markdown is definitely more author-friendly than HTML, but that's more like an extra.
cat header > index.html
cat page >> index.html
cat footer >> index.htmlHere's my stack: I write .html files in GNU Nano, and serve them with Apache. I've done that for about 20 years (with varying editors and servers), and I don't see why it needs to be any more complicated putting words on the internet. Yes yes, old man yells at cloud etc, but I'm a strong believer in "less is more".
Another 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.
I'd love to see a blog post on how your rust/org-mode blog works.
The main changes since that article is I use systemd services to manage caddy / webserver instead of tmux sessions.
The short of it is: rocket + tera + org-mode html export + some amount of parsing. There didn't exist high quality org-mode parsing crates when I made the blog.
You can learn more about the org-mode parts from the source code: https://github.com/dpbriggs/dpbriggs-blog/blob/f4936fa2dafea...