@ Smith on the SF position:
Well, I have to admit that I never saw him actually play that position - as I haven't seen a Wolves' game for years, so I will ask all the experts for their take on this. I do know that from time to time, he played that position, but in my opinion, he would play even more out of position at SF than at PF. With having now a plethora of players at hand that are either natural SF or better suited to play that position than the Cookie Monster, I do not think that it will become necessary to play him as a SF again, especially since he has now gained the muscle to hold his ground against PFs.
But - just like all the time - I guess it mainly depends on the matchups, since there are some slower SF around in this league who Smith might stand a chance defending against or where his physical strengh might generate such benefits offensively, that you are willing to take on the defensive gamble.
But I would welcome more first hand impressions by the other guys on the performances of Smith playing as a SF last year.
I am not sure if I would go that far to say I love him...but I liked him alot in his rookie season and am pretty sure that I would want him to get a chance to prove what he got (left) and what he can do to help this team. There a too many guards on the Wolves and we will inevitably need to get rid of some of them to balance the roster better. But writing Shaddy off just after his rookie and his first season after the dreaded micorfracture surgery...that would be far too early. I am not convinced that he still has the abilities that will earn him a longterm spot on this team, given the competition, but I am eager to see him try. But in both situations - earning a spot in the shortterm and contributing to the team in the longrun - I truly believe McCants isn't starting material in any team in the league.
But since you clarified that your lineup was more a \"wishlist\" of yours based on personal likings opposed to a serious lineup proposal, I guess I am fine with it ! Sorry that I did not get that in the first place.
The administrator has disabled public write access.