Dude, I never denied that those problems exist, and I have no beef with your language.
My primary points are:
1. Memory management has never presented itself as public enemy #1 in my personal career. Other things have always been far more troublesome.
2. For complicated programs that have been continuously developed and extended for decades, a re-write in a "better" language is not a particularly good idea.
FWIW, for new stuff, Rust is a good choice.
Also, being at Mozilla, I can understand why memory management seems like priority #1. You are a platform!
The rest of us are building on the shifting sands that the west coast creates. Keeping up with Microsoft changing this and Google changing that is WAAAAY more trouble than pointer arithmetic (for me anyway).
> 2. For complicated programs that have been continuously developed and extended for decades, a re-write in a "better" language is not a particularly good idea.
Can you explain the strategy you propose to stop the entire browser industry from getting knocked over at Pwn2Own every year?
If Mozilla thinks it's a good trade-off to spend the next several years fighting functionality bugs in exchange for better pointer and memory guarantees with Firefox, they are more qualified to make that call than I am.
For other types of program that I am familiar with, that is a raw deal. Take vim. I don't have it exposed on the network. I've never had any problems with it. It does not affect me in the slightest if the guys at a Pwn2Own can contrive some convoluted attack against it. The functionality is more important than the security is for my usage case. I would rather it just keep working than have it be undefeated at Pwn2Own.
At this point I think you're making an argument about software evolution more than programming languages. "Just keeping it working" is fine for software like Vim, which has a natural monopoly on the small niche of longtime programmers who have memorized the keystrokes and like it the way it is. (I am not insulting Vim users: I am one of them!) It does not work for software like browsers in a deeply competitive market, which have to cater to a large audience of hundreds of millions who constantly demand increased stability, security, and performance.
This thread has gotten so unwieldy that I now have more arguments than I started with! ;-) But yeah, evolution over revolution.
Perhaps that could be a fun challenge. Take some creaky old thing, have team A re-do it in Rust, have team B do an OpenBSD-style hackathon on it in its native language, let the QA guys and the hackers loose on it, and see which one fares better.
My primary points are:
1. Memory management has never presented itself as public enemy #1 in my personal career. Other things have always been far more troublesome.
2. For complicated programs that have been continuously developed and extended for decades, a re-write in a "better" language is not a particularly good idea.
FWIW, for new stuff, Rust is a good choice.
Also, being at Mozilla, I can understand why memory management seems like priority #1. You are a platform!
The rest of us are building on the shifting sands that the west coast creates. Keeping up with Microsoft changing this and Google changing that is WAAAAY more trouble than pointer arithmetic (for me anyway).