Live data from Hacker News

Mario Meets Pareto

mayerowitz.io

21–30 of 177 posts

Re: Mario Meets Pareto

#21
post #20

In Firefox reader mode, there's like 5 paragraphs of text. I am unable to digest the content on the website itself. Can someone confirm if the 5 paragraphs is the whole content or if I have large parts of it missing?

The article includes interactive graphs and scrolling animations that explain them, as well as data.

Re: Mario Meets Pareto

#23
post #16

Thanks! Very useful information. I will never play for Bowser again.

Once at a Mario Kart 8 tournament I was helping run there was a kid who had picked Bowser and max speed and he was struggling to make every turn. I switched him to the meta build and suddenly boom, he went from like 10th to 2nd against the AIs. It's kinda weird that you can shoot yourself in the foot so much when picking your kart in this game.

> It's kinda weird that you can shoot yourself in the foot so much when picking your kart in this game.

Nintendo optimises for fun, not competitive play. Infamously, to curb the competitiveness of Super Smash Bros (SSB) Melee, they introduce a random tripping mechanic in the following SSB (Brawl). Everyone hated it so they removed it in the one after that.

Re: Mario Meets Pareto

#25
> You probably won't pick a driver sitting on the edge of the frontier because you want some balance between speed and acceleration

for super mario kart speedruns go with bowser/dk: https://www.speedrun.com/smk/runs/zp68nr8m

That seemed to hold up for Mario Kart 8 too going with Bowser at the edge of their pareto frontier, https://www.speedrun.com/mk8

needing acceleration is a skill issue

Re: Mario Meets Pareto

#26
post #7
post #2

I did not understand https://news.ycombinator.com/item?id=49096439 , but I understood this.

I can only imagine the guy that made Mario Meets Pareto waiting for some Pareto related post to hit the front page before sharing his

I remember seeing this on HN frontpage already in the past, and indeed here it is: https://news.ycombinator.com/item?id=39936246

Re: Mario Meets Pareto

#27
post #25

> You probably won't pick a driver sitting on the edge of the frontier because you want some balance between speed and acceleration for super mario kart speedruns go with bowser/dk: https://www.speedrun.com/smk/runs/zp68nr8m That seemed to hold up for Mario Kart 8 too going with Bowser at the edge of their pareto frontier, https://www.speedrun.com/mk8 needing acceleration is a skill issue

Adding skill is just another dimension to the calculation.

Re: Mario Meets Pareto

#28
post #2

I did not understand https://news.ycombinator.com/item?id=49096439 , but I understood this.

It turns out a lot of things are extremely accessible to a lot more people when you teach them as concrete, relatable scenarios in simple language with useful visualizations instead of abstract X, Y foos and bars described with an unfamiliar jargon term every 3rd word. We really need to do better when it comes to pedagogy.

Re: Mario Meets Pareto

#29
post #25

> You probably won't pick a driver sitting on the edge of the frontier because you want some balance between speed and acceleration for super mario kart speedruns go with bowser/dk: https://www.speedrun.com/smk/runs/zp68nr8m That seemed to hold up for Mario Kart 8 too going with Bowser at the edge of their pareto frontier, https://www.speedrun.com/mk8 needing acceleration is a skill issue

On the other hand, if you are a casual and want to dominate 99% races you enter at people's homes, pick Toadette (with Mr. Scooty). I don't think I've lost since 2019.

Re: Mario Meets Pareto

#30
post #15

This is a really important concept for developers. One aspect for developers that I see quite often is the assertion that "We can't have X without giving up more Y", most commonly "we can't have more security without giving up on user experience". With the Pareto idea in mind, we can see that that statement is true, if and only if you are in fact on the Pareto frontier of security and user experience already. However…

Yes, the difference between coding (writing software) and engineering (making informed trade offs about system design) is effectively bound up in analyses like those supported by concepts like pareto efficiency.

One should keep in mind though that not all problems have a neat solution. Many spaces have multiple efficient points that still need to be chosen from, and many pareto optimization problems actually become NP hard computationally when the problem is large enough.

Post reply on HN