A Quick Benchmark Of Mozilla Firefox With WebRender Beta vs. Chrome

[Weasel]

Ok, perhaps I spoke too early. Can you please clarify what you said on #50?

You stated: "C++ best practices is not real C++. Real C++ is just C with extra features (even the name says it all). You code with C mindset but with extra features."

Can you please tell me whether you consider the smart pointer templates and others like std::vector and std::bitset, which are acclaimed best practices, to be some of those extra features you talk about, or instead they are practices reserved to "incompetent morons"? And if you think it's at all possible to use such features and still program "with a C mindset"?

They're part of a library, the standard library. You don't need them, and if they add the slightest bit of overhead to your specific scenario I suggest you don't use them.

As for it "not being true" anymore, that's just your opinion and the other people who code wrongly and then whine C++ has overhead. Stop following their ideologies, even if they are part of the C++ committee.

[Marc.2377]

Ok, perhaps I spoke too early. Can you please clarify what you said on #50?

You stated: "C++ best practices is not real C++. Real C++ is just C with extra features (even the name says it all). You code with C mindset but with extra features."

Can you please tell me whether you consider the smart pointer templates and others like std::vector and std::bitset, which are acclaimed best practices, to be some of those extra features you talk about, or instead they are practices reserved to "incompetent morons"? And if you think it's at all possible to use such features and still program "with a C mindset"?

Edit: "Real C++ is just C with extra features (even the name says it all)" - this is just wrong. It was true, in the 80s and perhaps early 90s. Now it just isn't.

[Weasel]

The poor guy (Weasel, not you!) has no clue what he's talking about; let him be.

Actually you have truly no idea what you are talking about. The compiler doesn't know what's from "user input". There's no such fantasy bullshit. Only static arrays of fixed size can be enforced at "compile-time".

The compiler might be able to optimize if the array's max size is known to it (though it has nothing to do with the language) but that only happens if it's close to where the loop is, highly unlikely in most cases. For the compiler to know this, it has to 100% prove it in all cases. It cannot risk generating wrong code even in 0.0000000000000001% of cases, so it has to be a perfect proof.

Accessing stuff with .at() has runtime checks whether you like it or not.

Bunch of apes.

[Marc.2377]

What on earth are you blathering about? Best pratices with C++ are always zero overhead, boundary checks are enforced via typing at compile time and only checked on runtime of parsed from user input.

The poor guy (Weasel, not you!) has no clue what he's talking about; let him be.

[jacob]

Spoken like a true Rust fanboy. Nobody sane can defend this language.

And also "rational arguments" can't apply to something that was probably designed in a mental asylum.

Well I can't argue with that. Most people will never match your detailed knowledge of mental asylums.

[Weasel]

Wtf, everyone, stop feeding the troll. He's famous for his anti-Rust stance and thrives on you engaging him with rational arguments.

Spoken like a true Rust fanboy. Nobody sane can defend this language.

And also "rational arguments" can't apply to something that was probably designed in a mental asylum.

Wtf, everyone, stop feeding the troll. He's famous for his anti-Rust stance and thrives on you engaging him with rational arguments.

[Weasel]

IMHO nobody sane would listen to your advice as far as software development goes ;-)

IMHO nobody sane would listen to your advice as far as software development goes.

My opinion is > your opinion.

[Grogan]

Say no to the Firefox browser that requires you to use pulseaudio. Chrome works with Alsa. Pulseaudio is buggy and uses a lot of CPU resources. The Poetterisation of GNU/Linux is bad and Firefox do just that.

I can tell you that I did not like the sabotage of them disabling ALSA by default in a minor version bump. I didn't notice it during build (I used my usual .mozconfig file from the previous recent build) and it came up with no audio working. You have to explicitly enable ALSA support. That was a nasty thing to do and I did not appreciate the recompile... fry another egg on my CPU.

I used to have trouble with pulseaudio, but that is no longer the case. I'm over it. I don't even mind SystemD when used nicely... it's mostly the fast food distros that have rubbish behaviour.

[jacob]

No, it doesn't. Mozilla devs obviously wrote it in something that would be called incompetent++ rather than C++. I mean, the fact they rewrote it in Rust kind of proves this by itself.

Nobody sane would rewrite real C++ into anything else other than maybe C, especially not something as crap as Rust.

Also this is not a comparison between Firefox and pre-Rust Firefox you know.

IMHO nobody sane would listen to your advice as far as software development goes ;-)