161–170 of 201 posts
Earlier quoted context omitted.
Right, that's why I recently started checking people's profiles before posting a dissenting reply, and not making the reply if they've enough karma to downvote me.
If you care deeply enough about fake internet points to go to that much trouble, IMHO, you're doing it wrong. Are you feeling picked-on because of what you're saying, or how you're saying it?
edit: I'm working on being able to handle being wrong... usually flip out, like WHAT!!! You disagree with me?! (Contrary to my initial point about no bs)
Can someone explain the use for cloudflare at the end? I thought you can do the same thing just through your domain registrar?
Cloudflare DNS is one of the best authoritative DNS hosters in the world, if not the best already. https://www.dnsperf.com/ Cloudflare is also a great free CDN and has a crap ton of edge servers to make your static content serve quickly around the world. Has a lot of other great features too. Anycast ftw.
Holy cow. Is this an improvement? Remember in 1999 when you could get a static website up in 3 minutes using ftp?
That's how we do it in 2017. Want to handle an on-click? You need dozens of NPM modules and webpack. Look at Docker's cowsay "hello world" example - it has to satisfy several (dozens?) of perl dependencies just to render ASCII art.
Earlier quoted context omitted.
You could make a website with vi and host it on Solaris today if you felt like it. I'm not sure why would want to though. Things have improved. Now I use vim.
Yes, we do have better tools than vi now: Emacs comes to mind.
Earlier quoted context omitted.
I see both Jekyll and Hugo mentioned frequently in the "Using GitHub and X to host your website" space. Do you have any practical our technical reasons for preferring one over the other?
Having used both quite a lot, I much prefer Jekyll's template language as it's easier to use and more readable. It's a lot easier to install plugins to extend Jekyll as well. However, Hugo coming in a single binary makes it easy to get working when you come back to a site you've not updated in a while (my Jekyll toolchain was a combination of Ruby + Node + Gulp that felt brittle but could be improved with some work),…
Earlier quoted context omitted.
That's how we do it in 2017. Want to handle an on-click? You need dozens of NPM modules and webpack. Look at Docker's cowsay "hello world" example - it has to satisfy several (dozens?) of perl dependencies just to render ASCII art.
What does Docker have to do with cowsay? Docker does not develop or maintain the cowsay utility [0]. [0] https://en.wikipedia.org/wiki/Cowsay
Holy cow. Is this an improvement? Remember in 1999 when you could get a static website up in 3 minutes using ftp?