wibblewobble125

Docs came from a series of acquisitions https://en.m.wikipedia.org/wiki/Google_Docs#History

I’ve been using caddy for a year which does everything for you. Basically nginx/haproxy but with https built-in via LE, no fiddling about with cert files and brittle LE scripts, also supports subdomains equally easily.

Sometimes distribution is not for performance but tenant isolation for regulatory or general isolation purposes. I work in such an industry.

Bad reasons to trust code:

* “Many __informal__ eyes have probably looked at it”

* Lack of recent __number__ of (known) vulnerabilities

* “Serious guys” (appeal to authority)

I think you’re using short-hand, but perhaps the short-hand should be different. E.g.

* A list of audits by date, independent organization, is provided __here__ which is evidence of review

* The vulnerability acknowledgement, correction and release process is prompt, accurate and detailed, which is documented __here__

* XYZ coding, testing, fuzzing, proving, bounty, integration with other systems, documentation, defaults etc. practices are used in the interest in hardening the code, limiting moving parts, attack radius, etc.

YouTube commenters insists that Akira wanted to end Goku’s arc at Cell, but fanserviced beyond that. If true, explains a lot. I also felt that there was a lot of maturity and build up to the climax of the cell saga and everything afterwards felt like it undid that growth and just went on and on.

Amusingly, merit’s other meaning is the verb “to be worthy.”

I agree. I’ve been using Emacs for approaching 20 years. In the past few years when I upgrade I’m noticing the same thing. Some font faces have the wrong colors, in one case an actual function was removed and Emacs wouldn’t start, some commands prompt slightly differently. I like to point at Emacs as being like Linux, that it’s a stable platform I can rely on, but do have to admit that more recently I don’t want to upgrade for fear of breakage.

Hell, I’m still on a version of magit from 2014 because they wouldn’t stop moving things around despite it being, in my opinion, done. In all other software in my life I have to put up with things constantly changing for silly reasons, Emacs is the one piece of software where I’m in control.

I fully empathize with the poster being infuriated with changing behavior. I might not agree with the way it’s being expressed. It’s sort of “et tu, Emacs?”

As a small datapoint, I brought up Roc at work last year and a colleague said “it looked interesting but it’s the guy from Elm isn’t it?” and brought up this.

As a manager, I empathize with the frustration you were feeling. Steering a team or a community towards a vision is very hard. Just when you think you’re getting somewhere, someone does the exact opposite and mixes people up. It’s easy to lose patience. I’ve made similar mistakes on popular projects and was fortunate enough that no one publicized them. I was allowed to learn from my mistakes without being punished for it.

I don’t have any advice on this. It’ll probably turn out fine.