Even if this were true, it would be better if the archives were not available for some decades after the original posting. I’m OK with my content being analyzed by historians, but the definition of “historian” presumes some professional detachment that is not available short years after the post was made.
> I always understood that for a telephoto lens you wanted the f-stop number to be higher,
I suspect you are confusing f-stop (ratio of aperture diameter to focal length) and focal length ("zoom").
Also the f-stop marketing is annoying to me - the f/2.4 aperture on an iPhone lens is probably equivalent to like f/22 on an FF lens for most purposes.
The way I avoid stressing about this is by realizing that the iPhone camera is still way worse than a real dedicated camera with a large optical path (lens and sensor). If you care about good photos, the Pro Max won't get you that far in the grand scheme of things.
> Go is one of the easiest languages to write with a simple text editor.
As long as you never refactor anything.
> Rust is among the hardest due to its complexity and demanding static analysis
I have never wanted or needed to offload Rust's "demanding static analysis" to my text editor. Rust's linearity/lifetime type system is really quite simple - it's not like you have to keep track of long-distance lifetime relationships in your head.
Even a reasonably powerful type system with e.g. HKTs, arithmetic, etc. like Haskell's rarely benefits from external tooling, and any interactivity can often be just as easily done via a polling build tool like ghcid rather than integrating it into a text editor.
The one place where it strikes me as sane to have a "smart" text editor is if you're using a proof assistant-style language like Coq/Idris/Isabelle/Liquid Haskell/etc. where there's actually a non-trivial amount of interactivity required while writing the code.