I think it's great that some people don't care about the technology behind their blog and instead focus on writing, but this is taking the cake. I keep accidentally editing this blog post as I am reading it and there seems to be no easy way to stop it from happening...

edit: Oh my god, this is your product!? Please, this is a stupid gimmick. Middle click on X11 pastes the selection buffer, a critical feature for my productivity, and now when I try to open links in a new tab I end up pasting text I've selected.

That is a very positive article and it matches my experience, the only bleak outlook is:

"async has a relatively high complexity cost for us due to the 'static bound (cc), cancellation-safety, and restrictions relating to traits and dyn. These currently seem insoluble. Bifurcation between sync and async primitives and ecosystem idiosyncrasies further increase the async tax. Effects-inspired solutions seem unpromising."

"Pre-1.0 Rust had a solution: libgreen. It achieved concurrency in user-space without this bifurcation, but at significant performance, portability and maintenance cost and so was removed. With increased engineering bandwidth this may be worth revisiting. Again the language simplicity would be worth it. (One day I’ll create a PoC of zero-cost wrapping of std::{fs, net} plus fiber::{spawn, select} using generator!)"

As someone who dove deep into Rust at the end of 2022, I always find it interesting to read these stories from people who went through the harder times it was back in 2015. I feel lucky to have learnt the language when it was much more developed, as it certainly made the already steep learning curve a bit more comfortable.

In a way I feel like I'm going through what is described in the article but for Zig. I guess Zig is more or less in a similar place now to where Rust was back then. Still I enjoy very much using it already.

Accidentally clicking on anything resulting in accidental local deletions and modifications to the article is extremely irksome. Skill issue, I guess?

I feel rust promotes functional programming. I created a parser that would change its own state on an advance but the mutability and borrowing kind of made it hard to do it that way so I changed it so that the parser was stateless and had to return an index rather then adjust an internal index. Is it common for people to hit issues like this where the traditional pattern just doesn’t work and you have to do it a completely different way for rust?

I deleted a paragraph from the post. That was unexpected. Nobody really cares about large types though, right?

I suppose if I find anything I really disagree with I can correct it, so that's a bonus.

Async/await is the only thing prevent me from using Rust.

1. This site shows links in such way, that browser doesn't show target of the link in the bottom of the window

2. I've tried to re-use tab bu typing new URL into URL bar and it doesn't work, browser re-open same page and replace URL back!

WTF?!

Middle click doesn't work on your links btw. Oh... wait this is like some live editing view? What?