Then just not use it? You could even ask for a refund, I'm sure they'll give it to you.

That person in the audience was really grinding my gears. Just let the folks you're talking to answer you; no need to keep going on your diatribe when it's based on a false assumption and waste the whole room's time.

This sounds exactly like the type of nontechnical nonsense they're complaining about: attacking a strawman ("they're trying to prevent people from refactoring C code and making them rewrite everything in the current fancy language") even after explicitly calling out that that was not going to happen ("and to reiterate, no one is trying force anyone else to learn Rust nor prevent refactorings of C code").

It's also not clear how long they'd be able to keep that up anyway, given... https://techcrunch.com/2024/08/28/brave-lays-off-27-employees/

Desktop web apps are being looked at though, so there's that!

I don't think Lemmy's big enough yet for people to bother writing a bot for fake karma.

Great to hear! I've never used Redox either, so no idea how well that works too.

Oh sorry, yeah I misread (and almost did it again just now) - I thought you mentioned that they made Firefox a bloated mess back when you switched to Chrome. Apologies!

I'm not sure when something counts as hype vibes and what the problem with that would be.

It's a pretty good editor, way faster than VSCode on my machine, but I'm also missing a bunch of features. Those seem unimportant enough compared to the speed for now, so I've switched, but switching editors is easy, so I might switch back later. And if other editors get on my radar, I might try them for a bit too. Hype or not, no real harm done.

I'm very curious how buggy it's going to be. (Obviously very during alpha, but I'm talking release.) They seem to be betting big on customisability, and a myriad of different setups is like a fly trap for bugs, in my experience.

But at the same time, a modern language like Rust provides lots of help to prevent a bunch of them, and they might be very talented programmers, so who knows!

And then they made it a bloated mess and I went back to Firefox when they got their act together and opening the browser didn't tank ram usage

I don't think it was being turned into a bloated mess, as much as that it always was pretty slow, until Google started investing a lot in JS performance with the release of Chrome, and showed how fast it could be.

(Well, and as a result, websites started becoming more demanding, which did make browsers that didn't keep up slow down more.)

It's not hard to switch browsers, after all. And people know this. So of course they don't worry about it.

I think the author is lamenting this attitude: it's not hard to switch browsers, as long as those alternatives exist and remain viable. That gets less and less likely as fewer and fewer people use the alternatives.