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

121–130 of 275 posts

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

#121

Post by tilolebo »

gherkinnn wrote: post #117
tilolebo wrote: post #113

Earlier quoted context omitted.

>they're gonna be around for a long time how many months does that translate to in frontend dev time?

This meme is tedious. 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.

Six years, roughly the time it took Angular to rise until version 2.

Sorry for the sarcasm, I've been trying to learn web development for some months, starting with the basics (HTML, CSS, plain JS) and slowly adding more modern frameworks (Bootstrap, NodeJS, ...).

The course is a few years old already and it feels like 80% of what I learn is now completely irrelevant. I just wonder how frontend developers keep up with that pace.

If I'd write a blog, I wouldn't want to spend half of my time into refactoring and migrating to newer versions, frameworks, etc. But maybe that's just me.

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

#122

Post by ge96 »

encom wrote: post #6

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".

I'll make a basic UI eg. menu/side panel/body/basic write interface and then use LAMP. I can add additional capabilities eg. commenting/stats(view counting) if I want... don't think I personally need anything more than that. My stuff is dynamic eg. using TEXT for body through MySQL. I use Node now as a backend but for something quick I can still use PHP which is where I came from/started with. I can host images wherever/maybe add free CDN account.

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

#123

Post by screye »

flohofwoe wrote: post #77
jasode wrote: post #25

Earlier quoted context omitted.

>I wonder what sort of interactivity you want on your text? In case you glossed over it, I think he said it in his post: "But down the road, I may want to build a page that contains an interactive visualization, a filterable table, or a demo of a React component I'm open-sourcing."

I wonder if he actually tried embedding HTML into Markdown, because that's as simple and straightforward as it can be: just start writing HTML in the Markdown document, and after the closing element, continue with the markdown text. This should completely cover the requirement to embed interactive elements into markdown using a static site generator like Hugo or Jekyll without having to deal with an overly complex de…

I've been using Github pages with Markdown for my personal website and it is so simple and just works.

Haven't yet seen a reason to switch to anything else.

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

#124

Post by drej »

dan_can_code wrote: post #114
drej wrote: post #57

> 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.

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...

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

#125

Post by anderspitman »

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.

I second this. I'm all in on Markdown and other ASCII-readable formats. By all means, render out to HTML to make things pretty, but consider keeping the source in plain text. You can browse my personal site with curl or even netcat:

curl https://anderspitman.net/txt/19

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

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

#126

Post by flog »

I just remade my personal site after a 6 year break.

It took me 4 hours to redo a static HTML and CSS mockup, learning a bunch of great new things about CSS Grid and Vars... then another week to convert that static into a Gatsby static-generator site.

It's sort of insane how over engineered we've gone on this stuff. HTML and CSS are pretty great tools for a blog. We can skip the React, GraphQL, etc.

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

#127

Post by anderspitman »

flog wrote: post #126

I just remade my personal site after a 6 year break. It took me 4 hours to redo a static HTML and CSS mockup, learning a bunch of great new things about CSS Grid and Vars... then another week to convert that static into a Gatsby static-generator site. It's sort of insane how over engineered we've gone on this stuff. HTML and CSS are pretty great tools for a blog. We can skip the React, GraphQL, etc.

So... why did you convert it to Gatsby?

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

#128

Post by ryanbrunner »

joekrill wrote: post #86
woutr_be wrote: post #71

Earlier quoted context omitted.

> 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…

> I recently asked a front-end dev why they chose React for a simple app over simple server-side templating I don't really get this argument. What makes "simple server-side templating" better than React components? I'd argue that these React components effectively are templates. If someone is proficient in React, why are we suggesting they have to learn some other random templating language? Not to mention deal with…

If the argument is "what makes ERB / JST / some other templating language better than React for server-side rendering" then sure, there's not really much difference.

What I suspect was the intent of the original question was "why does a simple app need to be an SPA with an API on the backend", which I do feel is something that adds significant complexity to any project. It's sometimes worth it, but I'll never be convinced that having to maintain an API alongside client-side rendering is faster or easier than a traditional server-rendered application.

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

#130

Post by qnsi »

marvinblum wrote: post #115
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…

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
Post reply on HN