Implications of Rewriting a Browser Component in Rust

Re:Implications of Rewriting a Browser Component in Rust by alex_duf on Thursday February 28, 2019 @12:34PM (#19273142)

When comparing speed on the JVM with speed with native languages, the only positive side you get from native binaries is cold start nowadays.

For a webapp this doesn't matter, but as we're moving towards more cloud functions it start to make a lot of sense.

That needs to be ponderated by the fact any real life application will have to access the network at bootstrap to load configuration and therefore your bottleneck will most likely be I/O.

[ Parent | on HN ]

Re:Implications of Rewriting a Browser Component in Rust by chrisweekly on Thursday February 28, 2019 @12:48PM (#19273299)

> "ponderated"

Huh! I have a fairly strong vocabulary and thought this might have been a made-up word -- but apparently it means "to weigh down or give substance to", which aligns with your intended point here. TIL

[ Parent | on HN ]

Re:Implications of Rewriting a Browser Component in Rust by alex_duf on Friday March 01, 2019 @05:26AM (#19279317)

Sorry that's directly brought from French.

English is my second language. I did a quick google search just to make sure it was correct but it's hard to gauge if a word that happen to be in the dictionary is also widely understood.

[ Parent | on HN ]