> Often, it boils down to one common problem: Too much client-side JavaScript. This is not a cost-free error. One retailer realized they were losing $700,000 a

> Often, it boils down to one common problem: Too much client-side JavaScript. This is not a cost-free error. One retailer realized they were losing $700,000 a year per kilobyte of JavaScript, Russell said. Boy that's a lot. You know recently I tried writing "just browser native javascript" for my little baby website. It's all through Github pages, so they give you a nice little server that you can use based on your git repository. It's shockingly nice, and also shockingly easy to get stuff done with just vanilla JS. I wonder how much I could get done if I weren't terrible at CSS, haha. That's really the only thing holding me back from making my site appealing to look at. The JS is honestly very easy, it's a simple language to use and the browser is an awesome environment with a billion and one tools ready for you to use. But CSS, man. Every time I try to style something it winds up looking like a 2002 haunted house nightmare.