Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
PsychedelicShayna committed Dec 13, 2023
1 parent 57f7d8b commit 0eb0cb3
Show file tree
Hide file tree
Showing 3 changed files with 1 addition and 0 deletions.
Binary file removed .github/screenshots/buildtime.png
Binary file not shown.
Binary file added .github/screenshots/timedbuild.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
1 change: 1 addition & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,7 @@ In the process of working on this, I started writing my own JSON parser, until I

That being said, I'm not insane. While sending an HTTP request over a TCP socket and extracting a substring are both trivial tasks, inflating GZip compressed response data is not. Thankfully, writing FFI bindings to `zlib`, a library present on practically every single Linux installation, is trivial. That means that this utility technically does have one _"dependency"_, in the same sense that `cat` may be a dependency of a shellscript; `zlib` is ubiquitous. Yet, unlike a crate, you can't even tell:

![](.github/screenshots/timedbuild.png)

I'd be lying if I said that there isn't a "for fun" factor involved too, but I do genuinely think that some programmers are too quick to overestimate the complexity of certain tasks, and default to using a library (\*cough\*, leftpad), and that mentality can stop you from ever learning how simple it was the whole time. Seriously, making an HTTP GET request.. is just writing plaintext over a TCP socket. If you can format a string and write to a file, you can format a string and write to a socket. There's no witchcraft involved here.

0 comments on commit 0eb0cb3

Please sign in to comment.