voidlogic

Right but a Google L6 is a was probably a PE at the last Fortune 500 they worked for.

Why do you think the engine is beyond saving? I use Firefox everyday and have absolutely zero complaints...

You can still run firefox as normal app, and it's rock solid.

Hey, I live near you. Agree on multiple points. I doubt most people from the coasts would believe how good the food and drink scene in Winona and La Crosse is.

You are changing your view of the hard worker mindset based on experiences with a single individual?

Everyone I know in the API / CDN / Proxy space switched from using ab to wrk years ago for good reason. PSA: Please stop using ab and use wrk/wrk2. ab doesn't even support HTTP 1.1...

Most of your above list would be taken care just by sticking to Ubuntu on Thinkpads using gnome-session-flashback. Its basically a polished version of the same DE I have been using since 2004 and love... rock solid (not of the boot or HW issues you mentioned, etc). I spend like no time ever messing with it and its been that way since 2014, 2016?

I still don't understand why someone would want to use this over GOGS....

At my college all the dorms had a kitchen for residents to use in the basement... is this not normal?

I find Go's approach to be in the Goldilocks zone. Its not intrusive enough to slow me down (or guarantee correctness for that matter...) but its enough that I no longer need to save the multi-threading something I know needs to be multi-threaded for a second pass and very rarely have multi-threading issues or trouble debugging.

That being said, developers often have a bit of learning to get there, but that can greatly be accelerated by good team/mentor code review and discussion.

Also of note is having to terminate a single TCP/TLS connection per client vs one for every concurrent client request! Even if you are using a middle man like a CDN doing HTTP 1.1 pooling this is still reducing the established TCP/TLS connections by an order of magnitude or more.

This code should just call sha1.New(). If for some reason these allocations are a performance issue it is very simple to fix that will a little pooling:

    package main

    import (
        "crypto/sha1"
        "hash"
        "sync"
    )

    func main() {
        hasher := getHasher()
        defer poolHasher(hasher)
    }

    var hasherPool sync.Pool = sync.Pool{
        New: func() interface{} {
            return sha1.New()
        },
    }

    func getHasher() hash.Hash {
        return hasherPool.Get().(hash.Hash)
    }

    func poolHasher(hasher hash.Hash) {
        hasher.Reset()
        hasherPool.Put(hasher)
    }