Comment by SuboptimalEng
4 days ago
I started a portfolio website with Netlify (iirc), then I moved to Vue + Gridsome (on GitHub pages), then Next.js with Tailwind CSS, and was about to move to Vite.js over winter break.
That's 4 stacks over the course of 5-6 years. Not worth it.
Decided to do the sensible thing and use GitHub's README functionality. I prefer this approach and wish more folks in the tech community adopted it: https://github.com/SuboptimalEng
This is an interesting idea! Honestly I didn't even know Github had a per-user readme until you mentioned it
IMO there's quite a surprising amount of stuff you can do on GitHub that's highly undiscoverable. You only think of it when you see someone else on the site doing it, and then you don't necessarily know what it's called so you don't know how to research it.
I hate the UI layer, for this reason. Nothing is ever stable. I'm looking for "Boring" and "Googleable in the age of AI slop". The other alternative are frameworks small enough to easily comprehend.
The UI is often tangential to the heavy lifting done by the back end. It often needs to be "just good enough".
Don’t hate the layer, hate the player.
How can UI be stable if you’re the one changing it all the time even if all you need is a readme page that can be done in the same UI with no change for decades?
GitHub was just down the other day. Why would you want your personal website/portfolio to be tied to GitHub? Crazy "modern web dev" stacks are likely overkill, but that's not an argument against self-hosting.
Personal websites can be down a few days a month without a problem.
+1. Not like my $5 hosting plan has less downtime than Github. Well... maybe? Fewer moving parts perhaps. But it's not immune.
Because it's free and convenient, and other hosting providers don't magically have 100% uptime either. Not even necessarily more uptime than GitHub.
I like to think that when GitHub (or Google, or Netflix, ...) are down, I am not alone.
A few million people are holding their breath - unlike in the case of my self-hosted site where I am alone to bring it back online.
How is it "tied"? You still have a local repo that you could deploy somewhere else.
sounds like a self-inflicted problem really. Why do you even change stack that much if what you want is a simple functionality?