4 ms·
No offence, there's a bit of stubbornness when someone says, "I used an FTP client to upload whatever I wanted by a process that was pretty obvious." Git + Page
by shubhamjain 3y ago
No offence, there's a bit of stubbornness when someone says, "I used an FTP client to upload whatever I wanted by a process that was pretty obvious." Git + Pages/Netlify is a different setup than FTP for sure, but it isn't more complicated. Just connect your git repo with Cloudflare pages and push things to it. If you don't like CLI, there are plenty of git clients to do the job. Hell, you can edit files on Github repo itself.
The reason I say this is, because as I have grown senior, I started noticing similar stubbornness in myself ("This was so much easy back in our days") and attitude of refusing to learn that came with it. I don't deny that some of the complexity in the web world is unwarranted, but when I refuse to invest my time in even trying to understand new solutions, I fail to acknowledge the benefits as well.
In the FTP days, it was easy to crash the whole site because of bad code that creeped in and no easy to way to decipher what change caused it. Cloudflare pages allow my to restore my site to any point of time and makes it easier to keep track of changes.
I think it's important to keep an open mind when it comes to new solutions.
- ryandetzel 3y agoAgreed. Once you get over the small hurdle of learning something new often times the new confusing method is much easier than the old way.
- Michelangelo11 3y agoThe issue is not, as you call it, refusing to learn new things. The issue is that it's relatively hard to find solutions for your problem rather than the very biggest and most complex problem -- in other words, trying to find something to kill a housefly with and only being offered field artillery. The benefits of Cloudflare pages that you describe are certainly very real, but for a static site consisting of a couple of files that's built by a reasonably experienced person and that will receive essentially no ongoing changes, they're not needed -- so all the extra complexity of CF pages is unjustified. If I were building a reasonably high-traffic commercial site with a JS framework, a backend, user accounts, and so on, I'm sure I would be genuinely grateful for CF Pages' features, but I just need to kill a housefly and I don't want to spend time wheeling field artillery into position.