Mario meets Pareto
mayerowitz.io
Mario meets Pareto
1–10 of 184 posts
Re: Mario meets Pareto
#2[dead]
Re: Mario meets Pareto
#3Beautiful presentation. I love when visualizations serve the goal and not the other way around. Tufte would be proud.
Re: Mario meets Pareto
#4Excellent article! Super approachable and relatable, making it very good at explaining a useful model.
It immediately has me looking for other places to apply this. This'll be top of mind for a while!
Re: Mario meets Pareto
#5This excites me to consider using it as a design tool. When trying to design a game with a more large pareto front of fun and viable builds.
Re: Mario meets Pareto
#6I really like the article and the presentation!
With that in mind, is this style of presentation (i.e. different elements jumping out or moving into focus as you scroll down the page) easily doable OOTB with any JS libs? Or is this pretty much a custom job?
Re: Mario meets Pareto
#7One thing this should mention is what game version it uses. Updates frequently change the stats and thus what builds are “best”.
Re: Mario meets Pareto
#8Wait, Bowser and Wario are the fastest? I thought it was the other way around. I guess it's reversed from Mario Kart 64.
Re: Mario meets Pareto
#9Well... that was a seriously impressive presentation. I already knew about Pareto efficiency/the Pareto frontier, but now I'll never be able to forget it. And I'll think of Mario Kart (and poor Koopa being dominated) every time.
Re: Mario meets Pareto
#10Wait, Bowser and Wario are the fastest? I thought it was the other way around. I guess it's reversed from Mario Kart 64.
They have the highest top speed. It was that way in Mario Kart 64 as well. They have the worst acceleration though.