When comparing Linode vs GitHub Pages, the Slant community recommends GitHub Pages for most people. In the question“What are the best hosting solutions for personal websites/blogs?” GitHub Pages is ranked 1st while Linode is ranked 8th. The most important reason people chose GitHub Pages is:
One of GitHub's features is a very powerful web editor which helps users edit or even create files right from the web browser, once the file is saved it's the same as a commit. Coupled with pages, this tool becomes even more powerful, giving users a free CMS that is easy to use and create.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Excellent support
Linode's support is amazing. Tickets are usually answered within minutes, if there's a network or hardware issue it's usually resolved before anyone even notices.
Pro Gives you the chance to fix problems without relying on support
If you mess things up in your Linode instance, for example with the filesystem or boot configuration, Linode allows you to run a recovery ISO so you can try and fix things yourself without relying on Linode's support team.
Pro Speed
Their VPSs are very fast.
Pro Allows you to do things that usually can only be done if you have access to the hardware
Linode allows you to create memory partitions and copy or move them around. Furthermore, it even lets you reboot your instance with smaller RAM in order to simulate how your application would act if your Linode instance gets downgraded.
Pro Comprehensive, well documented API
The API gives access to nodes, nodebalancers, stackscripts, DNS, and accounts.
Pro Provides SDKs for several languages
SDKs are available for Python, Perl, PHP, Ruby, Java, and Node.js.
Pro Stack scripts
Stack scripts gives you the chance to build a completely custom Linode stack with multiple custom features and options all run automatically and set up.
Pro New Cloud Beta user interface
A new user interface is under development which will still keep the same level of power Linode offers but with a cleaner interface. Showing forward thinking and continued improvement.
Pro The ability to create and edit files on the web UI gives GitHub pages the same power as a small CMS
One of GitHub's features is a very powerful web editor which helps users edit or even create files right from the web browser, once the file is saved it's the same as a commit. Coupled with pages, this tool becomes even more powerful, giving users a free CMS that is easy to use and create.
Pro Supports Jekyll
A simple, blog-aware static site generator, Jekyll makes it easy to create site-wide headers and footers without having to copy them across every page. It also offers some other advanced templating features.
Pro Supports custom domains
A custom domain can be added by creating a CNAME file with the necessary domain in the root of the repository and adding/changing corresponding DNS entries.
Pro Free tier
Static websites can be hosted on GitHub Pages for free as long as the repository is public. Private repositories start at $7/mo.
Pro Allows for all the git features when building your site, too
Cons
Con Backups have become unreliable
I've been a Linode customer for 10+ years, but over the past 3+ years their backups have become unreliable, which is unacceptable for a paid extra to the service. I've had multiple issues with backups failing, and restoring from a backup has caused my VPS to fail to deliver website content for reasons neither I nor Linode support could figure out. In the end, I just had to rebuild the server from scratch with a personal backup.
Con Not really suitable if you have a very heavy CPU application
They'll cap your usage if you go above 80% for a sustained period - even on very large expensive boxes (if you use Load Balancers offered, this can be mitigated).
Con For more advanced users
Can be an issue for those not used to setting up their own server. Managed services are really expensive if help is needed.
Con No self-help migrating option
If you want to migrate to another hosting solution from Linode, you can't do it by yourself. You have to open a support ticket.
Con Treats customer as a liability
Many malpractices in the name of machine abuse. Their machines get abused with just 10% steady cpu utilization.
Con Unable to set cache expiry, must accept GitHub defaults (which are short)
Low cache expires - GitHub sets the cache-control: max-age header to 600 seconds, or ten minutes. Normally, you would set this value to a year so that it stays cached, and then use fingerprinting on your assets. Instead of serving style.css, you would serve something like style-62c887ea7cf54e743ecf3ce6c62a4ed6.css. As it stands now, assets are rarely going to be cached on repeat visits.
This will give a low score on https://developers.google.com/speed/pagespeed/insights with a 'should fix' recommendation around 'Leverage browser caching'.
For a high traffic site this may have implications