Browser Support • Re: Why is Pale Moon so slow?

Then there's also delayed response when switching tabs. Not as much on startup, but gets worse.

I've been watching a lot more youtube vids this week, and that's the slowest site ever. Yet we're talking about a few seconds (3-5) of initial "activation" at most.

YouTube in its current form is considered unusable for me. I only still access it through Project VORAPIS.

Patience is a virtue.

I've been patient for a long time, but it's run out and my nerves are no longer as good as they used to be. These seconds pile up.

Off-topic:

I do care when in mysql I issue a "select" statement and I haven't set up proper indices on some table. There I feel the difference between 0.x sec ("instantaneous") or 5-10 sec or more ("slow" ... and sometimes my perception is "much slower" than the time indicated as execution time)

Non-optimal InnoDB buffer size can also make things pretty slow.

Then adding new columns to large tables is notoriously slow. And to some extent creating tables too. Especially on Windows. Watching software at work's log when it's creating tables (currently 176 of them) on MySQL, taking its sweet time. While on MS SQL, it just blazes through.

I once compared migrating data from one larger SQLite database, migration to MySQL took over 50 min while just little over 10 min to MS SQL.

We only recommend MySQL to cheapskates who refuse to pay for pro version of MS SQL. Though MS SQL Express was recommended in the past as well and I guess it's OK if their database isn't growing too quickly or they don't mind having to delete old data.

Google is a corporation, they should have no right to push their own agenda... corporations usually have bad intentions which is why this is bs what you said.

What was bs? I merely stated what garden JavaScript and Rust originally grew on.

As for both Goanna and Blink supporting constructs the other doesn't understand, that's the fact too.

At least this one thing doesn't work in Gecko or Blink:

CODE:

try { // code where error may occur} catch (ex if ex.expression) { // error handling if condition is true}

Or:

CODE:

var users = { jon: { username: 'Jon', genrePref: 'rock' }, lucy: { username: 'Lucy', genrePref: 'pop' }, mike: { username: 'Mike', genrePref: 'rock' }, luke: { username: 'Luke', genrePref: 'house' }, james: { username: 'James', genrePref: 'house' }, dave: { username: 'Dave', genrePref: 'bass' }, sarah: { username: 'Sarah', genrePref: 'country' }, natalie: { username: 'Natalie', genrePref: 'bass' }};for (let [k, v] in new Iterator(users)) { console.log(`${v.username} | ${v.genrePref}`);}

Though perhaps this one just doesn't behave like documentation describes (Iterator is supposedly not constructable on its own) rather than being some specific Mozillaism.

Don't know if there's any more such constructs.