d4n3

Great idea... I don't mind paying for good games, but what i do mind is games that try to squeeze as much money out of you for just playing it, which fits your definition of bullshit games.

So unlockable DLC and removable ads are fine, but endless pay-to-win consumables aren't.

Sorting by number of reviews would be great - it's a better indicator of popularity than the review score

It seems like you're comparing current conversion rates vs. past conversion rates.. Did you try AB testing this side by side? It's not necessarily only the effect of image optimisation, could be just organic growth of your site?

I think this actually wasn't an arbitrary choice, but a result of the algorithm.. e.g. factors are displayed as clusters ordered in a circle (factors of 2 is a circle with groups of 2, factors of 3 is a circle of groups of 3).

So for primes, you have a circle of groups of 1.

Very cool visualization... I wonder how they get their data?

you could probably combine this with the font-face trick to target different letters

you could combine this with ::first-letter and custom selectors for each item of interest to get more specific data from targeted page elements...

If there was a way to target n-th letter in css, you could also get the full plaintext of an element with a huge number of font-face / selector combinations

Chrome devtools sort selectors by specificity by default and you can quickly see what order the selectors / properties were applied in and what overrided what.

Most of the !important uses I've seen are more due to "Why doesn't this work? Dunno, I'll just put !important on it.."

Since !important only applies to a specific property, it's not that useful for making structured CSS components, and makes it harder to override (using !important again on every property)

I can't think of many cases where using !important would be better than overriding with specificity. Maybe when using 3rd party styles or making styles that are embedded in an external page (e.g. widgets).

> as they seem not fully aware of the standard order of conflict resolution

I'd say it's the other way around - a lot of usages of !important are due to lack of understanding of CSS specificity, usually as a symptom of something else like using IDs in selectors..

If you avoid using IDs in selectors and avoid deep nesting of classes, then overriding styles works as you expect - apply a more specific selector to override the style.

Selector order only comes in to play rarely, and you can structure your files to start with less specific (base) styles first.

I see !important as more of a workaround than a solution, and I don't think it is used as it was originally intended.

There' a user switcher button in the top right corner, you can have multiple browser sessions with seperate histories / cookies (e.g. work / personal)

Right, with lots of elements, React still needs to render and diff each component which for a lot of elements causes a lot of garbage and diffing work. ShouldComponentUpdate / PureRenderMixin avoids this altogether when props/state isn't changed so this gives a significant boost with lots of elements.

PureRenderMixin is basically shouldComponentUpdate with a shallow comparison of previous/next props and state, but the big win is avoiding render and diff for the component, so returning false would be about the same as PureRenderMixin.

PureRenderMixin would defenitely help here, even to the point where it's comparable with the js solution.

Even though keys help here, render is still called for every image every time and then diffed.

He'd have to extract the image divs to a component and put PureRenderMixin on it so that the component's render is skipped altogether.

For me it was trying to index a huge folder containing images, you can use project settings to exclude some folders with the folder_exclude_patterns setting.

I think modern browsers prevent cross-requests to local subnets so this may mitigate CSRF