Ben Simmons Would Vote for Luka Doncic as ROY over Trae Young, More

Philadelphia 76ers' Ben Simmons (25) in action during an NBA basketball game against the Brooklyn Nets, Thursday, March 28, 2019, in Philadelphia. The 76ers won 123-110. (AP Photo/Michael Perez)

Michael Perez/Associated Press

Last year’s NBA Rookie of the Year, Philadelphia 76ers point guard Ben Simmons, told Keith Pompey of the Philadelphia Inquirer that he believes Luka Doncic should win the award this season.

“He’s playing better,” Simmons said of Doncic. “His team is winning more games. Trae Young is killing it. … But overall, I think Luka’s got the team playing better, and he’s just doing a little bit more.”

It’s only fitting that Donovan Mitchell—last year’s runner-up for Rookie of the Year—disagrees with Simmons and thinks that Young should get the nod:

For much of the season, Doncic has been the front-runner and prohibitive favorite to win Rookie of the Year. But Young’s continued improvement has at least made it an interesting debate.

The Dallas Mavericks are 30-46 on the season in the deeper Western Conference, while the Atlanta Hawks are 28-49. Slight advantage goes to Doncic here.

Doncic, 20, is averaging more points (21.6), rebounds (7.6), has a better field-goal percentage (42.5 percent) and has six more triple-doubles than Young (seven overall). Young is still averaging a solid 18.9 points per game and is averaging more assists (8.0 to 5.9). He also is shooting slightly better from three (33.1 percent) and has six more double-doubles on the season (28 overall).

The statistical comparison is a push, with perhaps Doncic receiving the slightest of edges in this department.  But if the criteria were which player was performing better right now, Young might pull ahead.

He quietly has reached some absurd milestones as a rookie:

Both players are special, no doubt, and either would be deserving of the award. Simmons thinks it should go to Doncic. We’ll see if the voters agree.

Read More



from Update News Topic https://ift.tt/2FPqO2e
0 Comments