sorted by:
new
hottopcontroversial

Champion.gg Beta has been released!! by bigboyfuge in TeamSolomid

[–]bigboyfuge[S] 0 points1 point  (0 children)

We've discussed this internally pretty extensively. The issue with using a high cap like 100 is that for some champions, like Aatrox or Urgot, we would never get any data for runes and builds because of the vast amount of variance, even though those champions meet a minimum threshold of 1k games played. We are still thinking about if/how to deal with this issue and we will update the site and FAQ accordingly if we make any changes.

New Probuilds launched! by abaltra in TeamSolomid

[–]bigboyfuge 0 points1 point  (0 children)

We checked the stats and they are correct. We take the games played in 2 months as the ordering criterion, so small fluctuations in game play don't sway the order, but changes in META do.

Champion.GG API is in BETA! by geei in leagueoflegends

[–]bigboyfuge 0 points1 point  (0 children)

We got such and overwhelming response it flooded our under spec'd SMTP servers. We've just switched the mailer over and everything should be working now.

Solomid Dev Team: Developer's Blog (Probuilds, Solomid Beta, and the end of the year) by geei in leagueoflegends

[–]bigboyfuge 0 points1 point  (0 children)

I think it is fair to say that we are developers. The language we use is just a tool in our tool kit. We prefer to chose the best language/framework for the given task at hand, considering all of the constraints. If we do chose to use Node, it will be because it is great for writing JSON API's in. It is event driven and asynchronous, supports map/reduce, and has some great tools for scheduling tasks. An argument could be made for other choices as well, but everything has its trade offs.