diff options
author | Anthony Wang | 2024-11-24 14:12:53 -0500 |
---|---|---|
committer | Anthony Wang | 2024-11-24 14:12:53 -0500 |
commit | 04822b7b149ec9f6add66fcaa613f40b47b8ff7d (patch) | |
tree | 3be2fbad92830edbe372a6d28f680447b30a3914 /content | |
parent | 1e516e3396377376113f7e15394257ea24967838 (diff) |
Fix typo
Diffstat (limited to 'content')
-rw-r--r-- | content/posts/writing-masochistic-websites.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/content/posts/writing-masochistic-websites.md b/content/posts/writing-masochistic-websites.md index edc0c60..785d007 100644 --- a/content/posts/writing-masochistic-websites.md +++ b/content/posts/writing-masochistic-websites.md @@ -17,7 +17,7 @@ But what I'm going to prove to you today is that writing websites without JavaSc Enter [exozy.me](https://exozy.me/). A perfectly simple, clean website. It's looked exactly like that for ages (actually, more like about a year, but whatever). What you don't see is the rewrites it's been through. Although that website has always been pure handwritten HTML/CSS stuff, I've snuck in a tad bit of JavaScript here and there to make *my* life easier. The poster child for this is the [join](https://exozy.me/join) page which now uses a simple HTML form. But back then, this used... a simple HTML form. Yes, but with spooky icky [JavaScript](https://git.exozy.me/exozyme/website/src/commit/375086c30bcad2258717d67e25457a47394333bb/join/script.js)! -So you're probably like, that seems like a very very reasonable use of JavaScript totally unlike the convoluted spagetti that you see in your typical website's view source after clicking on the JavaScript files actually responsible for the page's bloat since the HTML source is one freaking line. And yes, you're probably like, I'd totally enable my JavaScript to run that even if normally I don't allow a single line of JavaScript to run in my browser to avoid all of its spooky ickiness. But no, I wanted exozyme's website to be 100% JS clean since after all, it's a privacy-focused site, and JS is usually public enemy of privacy #1 in the browser. +So you're probably like, that seems like a very very reasonable use of JavaScript totally unlike the convoluted spaghetti that you see in your typical website's view source after clicking on the JavaScript files actually responsible for the page's bloat since the HTML source is one freaking line. And yes, you're probably like, I'd totally enable my JavaScript to run that even if normally I don't allow a single line of JavaScript to run in my browser to avoid all of its spooky ickiness. But no, I wanted exozyme's website to be 100% JS clean since after all, it's a privacy-focused site, and JS is usually public enemy of privacy #1 in the browser. So I ended up moving that JS logic to the backend, so now some slow bloated Python API is doing all those username and email checks with regex that no one can understand, instead of it being in the frontend. |