Porting Resources [to IRIX] – Determining Viability

forums.irixnet.org

3 points·ladyanita22··6 comments

The obvious solution is to reverse engineer IRIX and make a modern version that runs on modern (non-MIPS) hardware.

Why they didn't do it during their push to Itanic or when they shot their feet helping generic PCs to gain SGI-level graphics is criminal.

Remember NeXT, who made 68K machines, ported NEXTSTEP to x86, SPARC, PPC and HP-PA.

" Rust in particular is resource hungry. Firefox's pre-Rust versions are MUCH faster in my experience than the equivalent Rust version. "

I had an idea this would be the case but according to every benchmark, Rust is up there with C++. Probably not the case in real life.

Yeah, I'm very surprised with this statement, coming from someone I'd guess should be knowledgeable enough. Benchmarks claim otherwise, and I don't think there's a single overhead you cannot escape from using unsafe. I'm not sure what this person is talking about TBH

Firefox is like 10% Rust, and is millions of lines of code. You cannot say "firefox feels slower now, must be the Rust" without actually showing that it's the Rust code.

Every benchmark of the components individually showed improvements when moving to Rust.

I understand you're part of the Firefox development team?

I am not. I was part of the Rust team.

Firefox is an open source project, so none of this is secret.

https://4e6.github.io/firefox-lang-stats/

https://hacks.mozilla.org/2017/11/entering-the-quantum-era-h...

Reply on news.ycombinator.com