the problem is that there’s people out there who in the analogy don’t know how to drive a car, defend it by saying ‘I’m just not a car person’, and constantly ask to be driven around when a major part of their job is driving a car. somehow when it comes to computers employers tolerate this

Which language would you say is not memory safe then? Is there any serious language out there where you should expect memory issues if you don’t make any mistakes?

sure, maybe, but performance doesn’t matter for deciding if a language is memory-safe or not. And C++ isn’t memory-safe by any commonly used interpretation of that word.

You may of course decide that the downsides of memory-safety aren’t worth it for your use-case, that is a separate issue

I agree that experienced users can write code that leaks less than in C, leaving aside the bottomless pit of despair that is undefined behaviour. But the the language isn’t memory safe, it doesn’t even prevent you from returning a reference to a local or helpnwitg iterator invalidation. you don’t have to jump through any hoops to enable making that mistake.

well, its possible to check if a rust equivalent would be riddled with raw pointers: just check the Servo code base.

personally I think its a good thing to have another browser implementation, regardless of specific choices they make about language or license