Good idea! I haven't and won't. Now read me the original text of Anselm's ontological argument and explain it in modern English without falling back to ancient philosophical gibberish like "substance" and "potentiality".
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.
I do not deeply disagree with your statement but I do not see the two as exclusive.
I think distributed public ownership placed in a corporation ruled as proposed here provides a chance to harvest residual good decisions from a citizen/shareholder who cares as opposed to having a single decision derived from some other issue a majority of citizens favor.
Unless you're talking about doing away with any kind of voting but Communism doesn't exactly have a stellar track record.
fwiw, Hoppe has become a darling of the extremist authoritarian "alt-right" (curtis yarvin, etc) but has been rejected by more mainstrean thinkers including most libertarian factions.
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.
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.
Microsoft isn't going to abandon C#, it's just using the right tool for the right job. While there are certainly cases where it is justified to go lower level and closer to the metal, writing everything in Rust would be just as dumb as writing everything in C# or god forbid, JS.
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.
I've bounced off that blog post in the past, because it makes it appear the first step to doing something in avy is to position all my files and "windows" (a "window" is an editing pane inside Emacs) in some clever way, and after I got all that setup, and the windows are all looking at just the right parts of the files, then I can move a paragraph from one window to another with just a few special keystrokes.
I feel like moving from a large monitor to a small monitor would limit the usefulness of avy; it's weird that the physical size of a monitor would limit a tool like this.
If I can only see 3 lines of text at a time (maybe an accessibility thing), the usefulness of Vim-bindings is not significantly reduced. Is the same true for avy?
Again, I'm willing to learn that I was wrong, but this is the specific issue that ended my enthusiasm for learning avy.
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.
I think that would be pretty disruptive, and would break some assumptions around crate integrity that are deeply held.
My understanding is that the left-pad incident is not directly analogous, since it involved restoring a deleted package rather than modifying an extant package.
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.
Had a similar experience, tried to switch to Meow twice, it's really nice in most ways.
But I found lack of vim-style repeat and accidental "dropping" the selection to be so unwieldy that I couldn't stick to using it.
Ended up writing an alternative to Meow which addresses the issues I had.
> What works best for me is no modal editing at all.
I used vim for 8 years and after switching to Emacs, realized that I'm the same. I was spending way more time (in vim) thinking about (to borrow another commenter's metaphor) how I was going to play the notes than what notes I was going to write.
I’m in the same boat. I’ve internalized Vim keybindings so much that there’s no friction between thinking and doing on the screen. If I want to place the cursor on the next line, move to the end and add a semicolon, then jump to the end of the file, I just do it. My pet theory is that because Vim keybindings are unintuitive, developing proficiency required building muscle memory, which offloads cognitive load from my brain to my fingers so text editing becomes mechanical rather than cognitive.
I also used to use vim and liked it, was running emacs with evil and it was ok… Then I started to write my config from scratch and got used to chords.
Later I tried boon, devil mode and meow but I just can’t get comfortable with mental overhead anymore. From those I’ve tried boon was the most interesting - some surprising QoL features, ergonomic layout.
What made chords bearable for me is a homerow mode on my Glove80.
