>Is there anything really wrong with a CPanel host with FTP upload?

Nothing, other than that it's not cool with the kids because it's the grandpa's way of being a webmaster.

Personally, being an old school grump, I'll choose FTP upload over Git nonsense any day of the week because why in the nine seas of the seven hells do I need to sign up for Github, upload all my crap there, download-install and run a Git daemon, feed it my Github login credentials, let the daemon download and sync/compile/whatever the code I have there, and then probably run the whole contraption through sixty dozen frameworks of JavaShit to have a website?

I'll just fire up Filezilla or whatever is the trendy FTP client nowadays, punch in my login creds, upload my crap that I wrote up in Notepad++, maybe have some fun with PHP because I'm old school, and be done with it. :V

Lots of us old school grumps still running things the old fashioned way for many years, serving millions of requests without issue, customers happy, and with a deployment pipeline anyone can understand :)

Because were more interested in getting things done, rather than tech fad signaling.

You over-focus on what's cool or fashionable. For many of us that's absolutely not the reason to go (or not to go) with a platform.

GIT is extremely useful for versioning. I want that. If I make a dumb mistake I want to have a diff that I've fixed a typo / grammar / added more links etc.

You neither need to use GitHub nor give your GitHub credentials to anything. You can just make a public repo and have it cloned / pulled-from by literally anyone interested -- why would anyone clone your public blog repo and re-host it? You can use sr.ht, Codeberg or just host your own GIT -- it's not that hard if you're into it (I am not).

Your way of doing it is fine but let's not pretend that everyone else is following fashion or coolness. That's very rarely true. There's a list of very good reasons to use a public GIT repo + Netlify + use a static site generator on your own machine to only produce a directory of HTML+CSS files.

Generally speaking, I subscribe to the philosophy of KISS.

For a multi-user environment where a dozen people could be accessing the same file at any given time, yeah some sort of version control system will probably make everyone's life easier.

For a single user environment as is likely the case for most static websites? Yeah, it's just needless complexity.

In fact, you lost me at "static site generator". WTF? Just write the damn HTML and CSS yourself, it's static after all.

This isn't to say your way isn't wrong /for you/, of course. Whatever floats your boat. For me, it's all just unnecessary complexity that will invite in all sorts of gremlins to waste my time.

> In fact, you lost me at "static site generator". WTF? Just write the damn HTML and CSS yourself, it's static after all.

At a minimum, static site generators create indexes, table-of-contents, tags, sorts by date, and other such features.

Pretty much no one writes good, raw, HTML these days. Documentation is written Sphinx, texinfo, docbook, and many other formats. Why? Because compiling chapters (or pages) together through static analysis is a very useful pattern for writing.

HTML is just an output pattern. Your actual words should be in a document generator at a minimum.

My website [1] is good raw (X)HTML [2]. It's just a couple of pages though, nothing fancy. If I was keeping a blog or something, I would definitely go for an SSG.

[1]: https://notpushk.in/

[2]: https://gitlab.com/notpushkin/notpushk.in

> It's just a couple of pages though, nothing fancy

Nope. Anything I can have a machine generate for me is fancy if I have to write it by hand.

> For a single user environment as is likely the case for most static websites? Yeah, it's just needless complexity.

Hard disagree. As I said above and you ignored it (no clue why): I want to have a history of my static website.

> In fact, you lost me at "static site generator". WTF? Just write the damn HTML and CSS yourself, it's static after all.

I can and I don't want to. Markdown is tons easier, you write out an article, execute one command, push the updated HTML+CSS files to GIT and you're done. If we're talking about simplicity let's not ignore that scenario because it really is quite simple.

I got a backlog of 30 things to work on and 500+ to check out "one day when I have the time". Going back to hand-crafting HTML is likely at spot #1784 in my brain. It's a meaningless paperwork that can and must be outsourced to computers.

Git for static site versioning? Why not just copy the HTML into a new folder? Takes seconds. Zero complexity. Gets backed up with your regular system backups.

Git is great for collaborative or complex projects, but for a static site, you're using a freight train to bring a single tomato to market.

Well, even though I can reinvent `git diff` I still don't want to. GIT gives me good diffs and I don't view it as an unnecessary overhead.

¯\_(ツ)_/¯

I'm fairly certain that was a joke

There’s a massive difference in quality and ease of use between cPanel and dreamhost custom panel.

I’ve been a customer since 2004

Well, I'm sure that's true.

But I guess my overall point is that CPanel is way easier than anything the original poster / author wrote.