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

201–210 of 275 posts

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

#201

Post by ivanfon »

PaulJulius wrote: post #172

I really think the negativity in the comments here is overblown, and misdirected. The author has a totally reasonable set of requirements: React + TypeScript, writing posts in Markdown, small amounts of interactability, and static site generation. It may be an indictment of the JavaScript ecosystem and the current state of the web that nothing exists that can help the user accomplish this out of the box, but that doe…

I just don't understand why a "static site" needs to download and run almost 1 mb of minified JS.

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

#202

Post by tyre »

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 did the same for my site (https://maddo.xxx)

Turns out html covers pretty much everything. Learned a few cool things along the way like:

- `@media (prefers-color-scheme: dark)` (Still working on nailing down color contrast there)

- doing footnotes via anchor tags that (a) automatically number themselves in text with counters and (b) automatically highlight the footnote using the `:target` selector.

not a single line of JS. The biggest perf issue by far is a font that's 64KB, which is probably including more than it needs to.

Deploying is 1 line of `scp`. Recently I got all fancy and added 30 lines of bash to support flags for only deploying assets or posts.

all of it is so fast. Coming from rails and react and all of that, it's refreshing.

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

#203

Post by jmondi »

_Understated_ wrote: post #159
bovermyer wrote: post #129

I would amend this blog post's title to be the following: "The ideal tech stack for a personal developer blog in 2020 where the author is a React front end developer who loves TypeScript"

That page of just text is a 1Mb download... Is this what the web has become now? Do we really need 1Mb of boilerplate for 10Kb of text?

I don't know where you got 1MB, the page for me was 363.09KB with caching off. That said, I do that React+TypeScript is overkill for a personal blog.

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

#204

Post by desert_boi »

jaredcwhite wrote: post #83

"I literally have zero memory of how we used to build forms in the pre-React times" Don't mean to pick on the author, but these sorts of comments scare the shit out of me. React is fine for what it was originally billed as (a library for building UI components), but the way people use it to take over the entire web stack is bananas. Definitely not needed for a static blog, LOL. P.S. Use LitElement anyway, not React.…

The meme about Web Components being the future is older than React at this point.

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

#205

Post by saagarjha »

dpbriggs wrote: post #84

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.

Eh, not sure about that one. I don't particularly like Ruby or Liquid but I run my blog on Jekyll because it is the right set of tradeoffs for me (works on GitHub Pages, produces a static site), not because I'm particularly invested in the stack. It works, I write things in it, from time to time I extend it to support some new thing I am putting in the blog post I'm working on.

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

#206

Post by saagarjha »

runawaybottle wrote: post #145
hawkice wrote: post #7

As a non-React developer: forms, before React, were actually super simple. The author mentions they forgot how to do forms the normal way, but like, can you imagine how excited they'll be by the simplicity?

Well, think about time just for a second. Take your average 25 year old frontend developer, for example. Five years ago in 2015, we were sort of coming out of Jquery. That means all these people had to be doing professional modern web development at the age of 20. What’s the likelihood of that for most people? Take you average bootcamper, by definition they didn’t know modern web development when they were about 22.…

You don't have to live through something to be aware of it. I'm not a web developer, and in 2015 I think I might have started programming, but even I have figured out that HTML forms are a thing that exist.

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

#207

Post by throwanem »

Wild to see so many people fail to realize that part of a "personal developer blog"'s job is CV support. From that perspective, it makes perfect sense to build it with the same technologies as the jobs you're looking to get.

But hey, I guess it's a lot more fun to talk about how somebody's hobbying wrong and they should've used Jekyll or Hugo or PHP or a shell script or a Python script or a Makefile or just hand-write everything and use framesets like it's still 1997 and the concept of user experience hasn't been invented yet. Carry on.

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

#209

Post by pjettter »

I dunno. Lately I've been into static sites based on Blazor with json files in blob storage. Fast, C#, no server. And no JS. Just C# to WebAssembly. In VSCode I can do dotnet new blazorwasm, then dotnet publish then publish to Azure blob storage via extension and presto. Yeah you can also put MarkDown files in DropBox and have some app pick it up and put it in your blob storage. No forms. Just your favorite Markdown editor.

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

#210

Post by gavinray »

runawaybottle wrote: post #145
hawkice wrote: post #7

As a non-React developer: forms, before React, were actually super simple. The author mentions they forgot how to do forms the normal way, but like, can you imagine how excited they'll be by the simplicity?

Well, think about time just for a second. Take your average 25 year old frontend developer, for example. Five years ago in 2015, we were sort of coming out of Jquery. That means all these people had to be doing professional modern web development at the age of 20. What’s the likelihood of that for most people? Take you average bootcamper, by definition they didn’t know modern web development when they were about 22.…

Haha, 23 year old developer here. First professional dev job at 18, coding since very young though.

> "Five years ago in 2015, we were sort of coming out of Jquery."

And HTML5 was still freshly standardized, Angular meant Angular.js, and your average web app was SSR MVC with view templates injected with controller variables, made interactive with jQuery.

Rails and MongoDB was the move, GraphQL would've been released the same year, and everyone would be convinced it was a fad and huge meme.

The React that would start to gain popularity around that time was a completely different ballgame. Redux wasn't hip yet, people were still using Flux from FB or Ken Wheeler's Flux plugin:

https://github.com/kenwheeler/mcfly

What a wild ride it's been.

Post reply on HN