Hacker News new | ask | show | jobs
by mrtksn 1919 days ago
Because the lines that do something are nicely categorized with documentation included. Instead of running it all, you can take a look what’s possible and apply it individually.
1 comments

> Instead of running it all, you can take a look what’s possible and apply it individually.

That's true of any script. The fact that this one is well commented doesn't make it not a script.

A cheat sheet is something you hang on a wall and glance at every so often. A script is something you run to make changes to a system. You can't run a cheat sheet.

How do you tell that it's not a really long string or a web page but a script? Maybe it's just a pattern of dots projected on LCD or 1s and 0s stored on a computer. I don't see any more concrete proof that it's not any of these but a script.
> How do you tell that it's not a really long string or a web page but a script?

`#!/usr/bin/env bash` is a bit of a dead giveaway.

I just see dots on my screen
How can you tell that a tall man in a trench coat isn't just a kid with a second kid sitting on their shoulder?

How can you tell if the series of dots you perceive as an LCD isn't just a photorealistic painting glued to the front of the screen?

How do know if your nervous system isn't just your bain in a vat connected to a matrix-esque electrochemical system?

How can you tell that anything you believe to be real isn't just a sophisticated simulation?

How can you tell if someone on hackernews isn't just making a specious argument just for the sake for arguing?