According to the blog:

What I’m about to introduce is a brand new OSS community chat app I’ve worked on solo, on and off, for the past 5 years. I believe it’s one of the closest public attempts at feature parity with platforms like Discord or Slack to date.

Without checking it, it’s likely that the first commit had already years of work.

Context?

How is this the first time I hear about mangoWC?

What are the advantages compared to searxng?

I probably have forgotten more programming languages than you can list, and if there are constants in programming, then a) while compilers get better at catching bugs, they never got over the basics, and b) a good programmer will alyways be better at preventing and catching bugs than a compiler.

I agree with this

Once you have aquired a good mindset about disciplined programming, those buglets a compiler (or even code review systems) can find usually don’t happen.

I also agree with this.

I would like to put a lot of emphasis in the usually. It doesn’t mean that they don’t happen, no human being makes no mistakes. Rust simply gives people a little more peace of mind knowing that unless they use unsafe they’re probably fine in terms of memory issues.

As a side note, there was this once I was making an ecs engine in rust, and kept fighting the compiler on this issue. Specifically, the game engine bevy uses Query in the World to retrieve information about the game state, and I wanted to do the same. For instance, in the following function (or something similar, I honestly don’t remember all that well):

fn getplayer(player: Query<Player>) {}

Would get player from the world and assign it to player (more or less). However rust was adamant in not letting me do this. After some thinking I finally realized why

fn getplayer(player: Query<Player>, player_too: Query<Player>) {}

Would give two mutable references to the same Player in the same function, which can be very easily mishandled, and thus is not allowed in rust.

I don’t know about the MISRA standard, but I don’t think that using it would have changed the way I coded my inherently flawed approach. This is a small example, one that didn’t even matter that much in the grand scheme of things and could be even hard to understand why it’s bad without knowing rust, but it is the one that came to mind. I think that if I had more experience I would he able to give you one that actually had security implications.

I’m no seasoned programmer, however

It’s the bugs that even evade a seasoned programmer that poses the problems, and there, Rust won’t help either

What do you mean these are not the ones that rust tries to fix? Even huge projects like the linux kernel get memory bugs. I don’t know anything about ADA and nor do I want to “evangelize rust” but what you’re saying sounds boggers.

Obviously rust cannot prevent all bugs or even most of them. It can only prevent a small subset of bugs, but saying that that “small subset of bugs” wouldn’t happen to seasoned programmers is just wrong, especially when you have tons of programmers working on the same big project.

I don’t mean to say that rust is always the correct choice, but that you’re waving off its greatest offering as bicycle training wheels (i.e. something no seasoned programmer would need)

Yep! What I wanted was for a “just works” experience as much as possible. Having to manually install lsps and treesitter parsers manually with nix felt like a bummer, honestly. It does work though

That is incredibly interesting. You didn’t have problems with treesitter failing to compile, or lsps and daps failing to run? What were the necessary packages that you installed? And how did you install lazyvim through home-manager, to begin with?

Wow I skimmed through your config and it seemed really good! This is really simple and easy to understand. I made this post because I’d wanted to keep my lazyvim configuration, but if I were to want to completely rewrite it with nix from the ground up it’d likely either be with nixvim or something like yours!

Description says the screenshot is at least 12 years old, though asking google at the time would have probably at least yielded the correct spelling of repository, so I wouldn’t go as far as to dismiss your conclusion

…What? Aren’t you the person who started this?