Keloo

How does it compare to the progress? Is the progress faster/slower?

Any links to read?

But Chrome is not free (well kind of). It saves lot's of money in royalties for Google (because Google search is the default search engine in Chrome). So even if it's 'free' it saves money for Google.

"typo"

400.45 :P that's a nice one

I've heard the opposite rationale. Having 'any' kind of mask decrease the number of times you touch your mouth or nose..

Infected People You May Know, got you infected.

Your Measurements Might Disappoint?

so that you don't have to pay royalties to other browsers for being the main search engine. I mean you have to pay one less. And if you have the most used browser, you save a lot.

I want to take a moment to appreciate the participation of the whole community on this. I've been following the story since it started and I'm very pleased to see how people (HN, Reddit, Github, etc.) came together to support the author and promote a more friendly Rust community.

There is a lot of criticism in the Software Engineering community in general but the Actix story made me feel way more welcome and open. I'm very happy to see that!

> I keep seeing Vim thrown up and down like it's the holy grail.

It's not. People tend to be religious about their choices, you can achieve the same result in any editor. Also most likely the bottleneck in your productivity is not the speed at which you manipulate text.

Anyway I will highlight few things that I consider great about vim.

1. It's more about consistency. (vim shortcuts are used in a lot of other places, ex: linux commands like `less`, `screen` etc.., tmux or other pane manager, etc..) When you learn linux you start to get a feeling about it, at some point you enter a command you somehow magically know the shortcuts to navigate/close/search inside there, Vim feels like a complementary thing to the whole linux environment knowledge.

2. It is everywhere! You need 0 time to prepare your work environment if you switch your job/workstation, and you also don't need to exit the remote machine/datacenter to write your stuff. You basically ssh into the machine[s]/datacenter and there you go, at the end of you day you just detach from the session, go home, and next day attach back and continue, all the commands, fancy log searches, processes monitoring, everything is there still running and waiting for you.

P.S. I also use VS Code sometimes especially for pet projects.