kangaroopouch

In the context of the linked article "velocity" is defined to be "Short and focused release cycles, aligned personpower, leveraging the community effectively". I think VS Code exhibits this value.

If you're interested in a reliably-quick-to-start editor, and prefer the Emacs ecosystem, consider https://www.gnu.org/software/zile/ . It's built for that purpose.

> But are there any other reasons, technical or otherwise, why people don't seem to use VSCode for things beyond editing code?

The best answer I've seen to this question is https://www.murilopereira.com/the-values-of-emacs-the-neovim...

Amongst other things, it lists different values that each tool prioritizes, and how "Core values are self-reinforcing. They attract like-minded people, who will then defend them."

Emacs: Extensibility, Freedom, Introspectability, Keyboard centrism, Stability, Text centrism.

VSCode: Approachability, Integration, Maintainability, Progressiveness, Velocity.

That is, even if VS Code achieves technical parity with Emacs (wrt introspectibility/extensibility), its community might not prioritize using VS Code for things beyond editing code.

Or maybe it will. These things are difficult to predict!

Ah it sits between the intro ( https://www.gnu.org/software/emacs/manual/html_mono/eintr.ht... ) and the reference manual.

Great to see resources being created for Emacs.

How does this compare to https://www.gnu.org/software/emacs/manual/html_node/elisp/in... ? That's a great manual and available in Info format (popular amongst Emacs users).

"If You're Typing The Letters A-E-S Into Your Code, You're Doing It Wrong" still applies, even though we now type chacha20. https://people.eecs.berkeley.edu/~daw/teaching/cs261-f12/mis...

We should aim for not having to fiddle with SSH config, and having sane defaults.

That could involve:

* cryptographers advocating changing OpenSSH defaults

* people refining their threat model to being able to accept weaker defaults

* Distributions or config management solutions that improve on the defaults in a careful considered way.

I use NixOS which generates my sshd_config. By default, NixOS:

* Disables root login via password: https://github.com/NixOS/nixpkgs/blob/8605fbd737e526c40ff8f0...

* Sets ciphers according to Mozilla's recommendations: https://github.com/NixOS/nixpkgs/blob/8605fbd737e526c40ff8f0...

Other distros, cfgmgmt, and container systems could do this too.

Which facts are discussed and shared is itself a function of bias.

Thus, seeking facts without considering bias is a recipe for bias.

On the one hand, I like this idea.

On the other hand, I prefer to avoid linking identities, especially in a publicly visible way.

I see how it's useful for those that do!

I'm comfortable with Emacs for programming, Org and RSS.

I've tried using email from Emacs a number of times, but never had a setup that I stick with.

All modes that used IMAP would block.

notmuch.el was nice but distributed read-state between two DBs, which felt brittle.

I use Thunderbird. I'm keen to use email from Emacs, if I can find a decent solution.