Auteur Sujet: Microsoft Developer Explains Why Windows Kernel Development Falls Behind  (Lu 963 fois)

0 Membres et 1 Invité sur ce sujet

ka9yhd

  • Invité
"In a response that truly seems to be from a core Microsoft developer, we are told about why Windows kernel development continues to fall further and further behind that of the Linux kernel. He says, 'The cause of the problem is social. There's almost none of the improvement for its own sake, for the sake of glory, that you see in the Linux world. ... There's no formal or informal program of systemic performance improvement. We started caring about security because pre-SP3 Windows XP was an existential threat to the business. Our low performance is not an existential threat to the business. See, component owners are generally openly hostile to outside patches: if you're a dev, accepting an outside patch makes your lead angry (due to the need to maintain this patch and to justify in in shiproom the unplanned design change), makes test angry (because test is on the hook for making sure the change doesn't break anything, and you just made work for them), and PM is angry (due to the schedule implications of code churn). There's just no incentive to accept changes from outside your own team. You can always find a reason to say "no," and you have very little incentive to say "yes."'"

http://tech.slashdot.org/story/13/05/11/1430259/microsoft-developer-explains-why-windows-kernel-development-falls-behind

Hors ligne melodie

  • Administrateur
  • Membre Héroïque
  • *****
  • Messages: 1744
    • Citrotux
This is kind of funny… The collaborative model is more efficient than the enterprise model, this we knew and if we didn't at least we strongly suspected so, and now we have the confirmation from someone within the enterprise... Very good find ka9hyd, thanks!
Good leaders being scarce, following yourself is allowed.