istlsfastyet.com VS Compass

> You want your website to work on vintage computers where they run super old browsers? Then you probably need a HTTP version of the website without TLS/SSL as it's not gonna be accessible otherwise.

That's incredibly niche. I don't think it deserves to be an example of "meme needs to die".

> Running a software/package repository/registry where every package is signed and verified locally? No need for TLS/SSL and it would just slow down downloading 1000s of packages as handshaking does add latency to requests.

Need some secure way to pass around the SHA256 (or whatever) hash you're using for verification.

And thinking of "memes that need to die", https://istlsfastyet.com suggests this isn't as bad as I think you think it is.

Not really... TLS is pretty much unnoticable on "modern" hardware. https://istlsfastyet.com/

So it's not correct to say that simply using TLS is faster than using TCP (see here). It is accurate to say that securing a connection allows engineers to take advantage of some incredibly clever work that greatly accelerates connection speed, and that wouldn't be possible without the strong security guarantees provided by modern encryption.

It was a big complaint with TLS as it was coming onto the scene: https://istlsfastyet.com/

> increases it’s overhead by almost 100%.

3.8/2.9 kB is a 31% increase.

1.16/0.62 s is an 87% increase.

But okay, let's round up to 100%.

The article is citing a page that counter-argues this:

https://istlsfastyet.com/

> But what about sites like https://doesmysiteneedhttps.com? While this website makes a few valid points, it still relies heavily on “fear tactics” that honestly don’t apply for the vast majority of users. It’s overkill.

Sorry, but not good enough.

1. "a few valid points": you avoid making your visitors liable in oppressive environments (employers, regimes), you avoid very real content injection (commercial or malicious), and you give the visitor a way to know that content wasn't tampered. That's a few valid points. (The rest of https://doesmysiteneedhttps.com are counter-arguments.)

2. "fear tactics": not true. Protecting the integrity of your visitors and your content is nurture, not fear.

3. "don’t apply for the vast majority of users": by making HTTPS standard at practically no cost, you make it work for those for whom it matters. Just because I feel safe on Hacker News doesn't mean that any visitor who goes here will be treated fairly by reading my message.

https://istlsfastyet.com/ (Is TLS fast yet?)

CPUs have specific features to help with encryption now, and HTTP/2 (which pretty much requires TLS) can actually reduce the number of overall TCP connections and may use less resources than clear text HTTP/1.1. Check out https://istlsfastyet.com/

pretty much gone, the beta site seems still to be alive http://beta.compass-style.org/reference/compass/css3/ and the github repo is still about https://github.com/Compass/compass/

SASS is a CSS preprocessor that is designed to be used as a standalone preprocessor, or as part of a framework called Compass. SASS for CSS is very similar to CSS, for creating CSS files that are more easily readable and maintainable than traditional CSS files. In the next chapper, we will learn how to use SASS to create a simple CSS file.

Soon after, Chris Epstein, the creator of Compass and co-creator of Sass, forked Brandon’s repository and asked for some help with the design. Being a big fan of Chris’s, Brandon jumped on the opportunity straight away. He pulled out the content, made the theme more generic, and named his creation Octopress.

I use a CLI tool to compile it as changes are made. I use http://compass-style.org/

Compass/compass - Compass is a Stylesheet Authoring Environment that makes your website design simpler to implement and easier to maintain.