This is beautiful, incredibly sane, and awesome reference material. There's no way I'd use a 3500 lines init.el or most of the extras, but somehow I feel like a good chunk of the stuff here should be upstreamed if we one day consider it reasonable to change default behaviors in a major update.
This is good and means no one can impersonate you using your phone number, but doesn't solve the recurring costs issue, you still need to buy a new number when someone registers yours, and every financial transaction puts you at more privacy risk. And is terrible UX, imagine having to add your contacts new numbers every other week.
And what happens when the next guy buys that same number and registers on Signal?
Phone numbers are recurring costs. And to keep a truly private one you must keep paying without ever disclosing personal info and that is really hard. Signal is a privacy nightmare for long term use.
Not really. Most people have terribly low time preference. Democracy for example is a very bad idea when you account for that (read Hoppe for a detailed explanation). Public company ownership is much better because it doesn't suffer from one vote per person, but still susceptible to much of the same management problems, specially in a society that already favors lower time preference by other means.
FWIW, all of those links compare Rust to languages created before 1980, and are all projects largely and unusually independent of the crates ecosystem and where dynamic linking does not matter. If you're going to use a modern language anyway, you should do due diligence and compare it with something like Swift as the ladybird team is doing right now, or even a research language like Koka. There is a huge lack of evidence for Rust vs other modern languages and we should investigate that before we lock ourselves into yet another language that eventually becomes widely believed to suck.
Disservice? Rust is taking over the world while they still have nothing to show basically (Servo, the project Rust was created for, is behind ladybird of all things). Every clueless developer and their dog thinks Rust is like super safe and great, with very little empirical evidence still after 19 years of the language's existence.
Zig people want Zig to "win". They are appearing on Hacker News almost every day now, and for that purpose this kind of things matters more than the language's merits themselves. I believe the language has a good share of merits though, far more than Rust, but it's too early and not battle tested to get so much attention.
Author is definitely correct in pointing out the incentives for companies to buy hardware. What the article misses is that there is in fact a reasonable economic incentive to not invest in software even if LLMs were not an economic bubble. It is that every single company is developing the same thing, there are many of those who even develop them as open source, and the ones that are closed as well as any company who would hire this guy, have a bunch of industrial spies inside anyway. Buying hardware may increase your moat, but developing software just rises the sea level.
Definitely not it's purpose. Avy can be used to select a word, line, or region. One action is move to it. But it can also, in it's own words, copy, yank, zap to, transpose, teleport, kill, mark, ispell, org-refile, and custom actions.
It's more about allowing a-library-fits-all than forcing it. You don't have to ask for io, you just should, if you are writing a library. You can even do it the Rust way and write different libraries for example for users who want or don't want async if you really want to.
If you're having to use Caps lock as control, modal editing is probably worth it. The one thing that makes non-modal editing far superior to modal, for me, is how easy it is to reach my Control key, as the palm of my left hand is always hovering over it and I learned to press it with my palm without having to ever move my fingers or hitting the wrong key.
I think the vim model in particular is great in terms of becoming muscle memory in like, a few months. It saves a few keystrokes compared to Emacs specially if you're counting Control as a key press. Navigating is a tad nicer with hjkl being next to each other. Having to press Esc after each edit just sucks though.
It's one of the best designed packages I've seen. Except 'repeat' that was horribly broken last time I checked but can be fixed by using the repeat-fu package. Manages to cleanly implement the kakoune model in an incredibly flexible manner and without interfering with anything else.
I still have my meow config, but currently disabled. The kakoune model is definitely what you're looking for if your desire is to edit text with the fewest keystrokes, it's far better than vim. I think the vim model is better, though, because motion-as-selection is fundamentally exhaustive, and in vim, by the time you realize what you're going to do, you go into operator pending mode (e.g. pressing d) and the next keystroke also feels obvious, while in meow you may have to reset the selection by doing some movement.
What works best for me is no modal editing at all. Definitely requires the most keystrokes, but that's not a limiting factor for me. It just feels nice never having to think about modes or constantly pressing Esc, and instead navigating with a mixture of default Emacs keybinds and great, joyous to use packages like Avy, smartparens, tempel and combobulate. Meow's KEYPAD is also not really helpful, it does save some keystrokes but doesn't make anything easier to remember or reach for. For the commands that it is worse, it is much worse.
>I have AI accounts and sling prompts all day long some days
This wasn't hard to guess. Beware of your interactions with LLMs creeping in when talking to humans. Best of luck! And I suggest you take heed of Simon's advice.