5 ms·
I used wintersmith.io. At some point it was abandoned and eventually the node version needed was old and other stuff associated with it. It became a hassle.
by mromanuk 2y ago
I used wintersmith.io. At some point it was abandoned and eventually the node version needed was old and other stuff associated with it. It became a hassle.
- eviks 2y agoWriting raw html and wiring it yourself is a hassle, how is not upgrading node a bigger one? Besides there are SSGs that are a single binary
- cookedcode 2y agoI promise you, HTML is not a hassle... It's markup. You describe the page, and then... you're done. And if you don't use weird, niche tags, it'll work basically forever.
- eviks 2y agoThis is a patently false promise. Yes, it's markup, but a bad one un-ergonomic-suitable for direct human consumption. Even the author of the blog understands it and uses alternatives > with md-block for markdown > You describe the page, and then... you're done Unless you want to re-describe something, of course. Maybe sort a column in a table...
- wink 2y agoI faintly remember when the kernel config asked you if you wanted both `a.out` and `ELF` support. No one says that single binaries compiled in the last 10 years might be usable without a VM in another 10 or 20 years. And no, 20 years for the same blog to exist isn't even so rare.
- eviks 2y agoIf you make such risks up, then no one says that html will be readable in the same way in 20 years (which is already kind of true as you have a lot of old blogs with awful layout on mobile) But there is an even easier one - nothing will happen to your html built files of 20 years, they'll remain... static. The worst is you'll go to updating your lovely html by hand, but you would've saved yourself wasting 20 years doing that instead of using a better system.
- bigiain 2y ago"the node version needed" Ahhh...