Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The ideal tech stack for a personal developer blog in 2020

vriad.com

Post reply on HN
Print view View original

131–140 of 275 posts

Re: The ideal tech stack for a personal developer blog in 2020

#131

Post by anderspitman »

swiley wrote: post #49
dusted wrote: post #34

Earlier quoted context omitted.

HERESY! The only true path is mine, I write .htm files in vim and serve them with nginx. Yes, I agree, cloudyelling or not, no stack is better. I recall in my teenage years, I built 2 or 4 "CMS" in PHP/MySQL, at the end, added all that AJAX when browsers blessed us with the possibility of making HTTP calls from JavaScript! But in the end, migrating from server to server, learning more about everything, the only thing…

Nginx? Why not busybox httpd with OpenSSL sconnect? So much bloat. :p

busybox and OpenSSL? So much bloat. My blog is browsable with netcat :p

nc txt.anderspitman.net 3838 <<< /txt/19

Re: The ideal tech stack for a personal developer blog in 2020

#132

Post by marvinblum »

qnsi wrote: post #130
marvinblum wrote: post #115

Earlier quoted context omitted.

This! I wrote my personal website [1] a few days ago (after it was blank for years) and went for concrete css [2] and plain HTML together with some Go code to serve the files. I set up a server on Hetzner Cloud [3] and my site was up within minutes using Traefik to get a SSL certificate from Letsencrypt. All in all it took me about 2 hours. If you start to play around with a CMS it can take you days if not weeks. Jus…

I heard in a jazz bar that you can host static sites for free at Zeit and use plain css for grid now, but I am unable to verify the rumours as my work limits Internet only to hackernews

Sure, but I'm on Hetzner anyways for different reasons. I didn't say it's ideal, just that it's simpler to write HTML+CSS sometimes. How you serve the files doesn't matter.

Re: The ideal tech stack for a personal developer blog in 2020

#133

Post by soulnothing »

karatestomp wrote: post #109

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…

I was trying to redo my project and consulting site. I did one side in hugo. The other I tried react and type script. I just said the heck with it.

I did a basic html page, using an open source css lib, cirrus[1]. Changes are very simple, and I use gitlab pages. My blog is still backed by ghost. But I think raw html is still very powerful.

[1] https://spiderpig86.github.io/Cirrus/

Re: The ideal tech stack for a personal developer blog in 2020

#134

Post by dan_can_code »

drej wrote: post #124
dan_can_code wrote: post #114

Earlier quoted context omitted.

Regardless of the dependencies, the point that it is the 'simplest, most elegant way to generate a static version of a React-based website' applies. Next.js is ridiculously simple to get up and running with - even for JS rookies.

That’s not the point I’m making. http://wipmoore.info/posts/2017/09/17/security-simple-vs-eas...

What point are you making? The linked blog post just defines simple and easy. I am not sure how this relates to your previous comment regarding dependencies.

> In essence simplicity is about reducing then amount of waste in development and increasing the longevity (service life) of the system we build.

I would argue the implementation of nextjs in the context of static, react-based a blog falls under this definition in your linked blog post. Unless I'm missing something?

Re: The ideal tech stack for a personal developer blog in 2020

#135

Post by karatestomp »

justinmeiners wrote: post #116
karatestomp wrote: post #109

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…

The primary advantage of markdown is that it is more readable in plaintext.

Yeah, but you lose lots of HTML features—not even layout-related things, which of course aren't present in Markdown, but things like image captions, , , and so on. I love it for cases in which plain text would otherwise be used but it's lacking a lot of really nice features in HTML that aid readability and accessibility.

Re: The ideal tech stack for a personal developer blog in 2020

#136

Post by dpbriggs »

marvinblum wrote: post #108

I recommended this on another HN post a few weeks ago: use Emvi [1] to write your blog articles and access them on your personal page on a server you control through the API to display them. You can store the HTML and attached files to serve it statically and update it from time to time. Should you decide to abandon Emvi you still have everything in place. I did this for a gaming community wiki (sort of, I don't stor…

Just wanted to say that I am impressed by the emvi landing page. Slick and high fps.

Re: The ideal tech stack for a personal developer blog in 2020

#137

Post by vekker »

woutr_be wrote: post #71
jcpst wrote: post #11

I’m sorry, but this is ridiculous for a static site. React and Typescript with embedded markdown? This problem has been solved a thousand times over with much simpler tooling. > I literally have zero memory of how we used to build forms in the pre-React times. :(

> I literally have zero memory of how we used to build forms in the pre-React times. This is honestly quite a disturbing trend with a lot of front-end developers these days. I recently asked a front-end dev why they chose React for a simple app over simple server-side templating, he's reaction was "we don't need SEO, so why do we need React SSR", like how does that argument even make sense. They seem to have forgotte…

Is it really? You might as well say it's been a disturbing trend that developers aren't familiar with assembly language anymore.

As abstraction on top of abstraction is created, it becomes easier and easier to write software, so naturally there are now more frontend devs who aren't familiar with web dev basics. And if all you have is a hammer, every problem will look like a nail. Similar trends happen for backend devs and in devops. Is that really a problem? Only if you are a company that hired them with different expectations.

Re: The ideal tech stack for a personal developer blog in 2020

#138

Post by test6554 »

karatestomp wrote: post #109

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…

I just converted a site to mostly static html because the old cms was out of date and nobody wanted to pay to migrate the site to the newest cms version (for like a decade).

Well eventually the hosting provider no longer supported such an old version of php and the old cms did not support the new php... So it was either re-code the whole site for the new cms or dump it to html and html (with php header and footer) won.

Re: The ideal tech stack for a personal developer blog in 2020

#140

Post by moreaccountspls »

karatestomp wrote: post #109

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…

I may have seen this on here, but someone made their blog with just html and the posix tool m4: https://github.com/technomancy/technomancy.us

If I ever make a static dev blog, I'm doing the same. I've tried hugo, and it just felt way overcomplicated for what I was trying to accomplish.

Post reply on HN