Wikipedia:Peer review/Criticism of Microsoft/archive1

Criticism of Microsoft edit

Any suggestions on how to improve this article :)? Thanks! Just another star in the night T | @ | C 01:56, 22 March 2006 (UTC)[reply]

congratulations on your bravery in writing such a work...this is a vry difficult topic because most of the proof of the premise is deeply hiddn in microsoft softwar...nevertheless you need more meat, more streamlining and less POV. the facts are devastating enough. here are some specific suggestions:
  • talk to some microsoft employees (or bettr ex employees) to seen how deep virus vulnerabilityt runs.

(most microsoft programmers wont even use int xplorer on their own home systems}

  • pursue vendor lock in (this is a big deal) microsoft seems to do the most damage here by embedding software glitches that interfier with vendors software they arent linked with
  • user unfrindliness: most users arent savvy enough to understand how poor the hierarchies are and how much bettr hierarchy could result if microsoft werent preoccupied with selling its allid services instead of guiding users. by the way their help hierarchy is really poor. i am an advanced user and i can often not find the right path

good luck on this important endeavor Anlace 14:33, 22 March 2006 (UTC)[reply]

  • Per WP:CONTEXT, years without full dates shouldn't be linked.
  • Could a citation be provided for Aaron Contorer's quote?
  • Despite doing a great job at trying to avoid POV in such an article directly about criticizing a subject, there are some weasel words. For example, "The company has been in numerous lawsuits by several governments and other companies for what some consider to be unlawful monopolistic practices. " and "Some accuse Microsoft's licensing policy of aiding the spread of viruses." Who are these some? I counted at least 11 incidences of the use of "some" as a weasel word.
  • Web citations could use the citation method provided by WP:CITE (perhaps consider using {{Cite web}}
  • Thanks, AndyZ 00:35, 23 March 2006 (UTC)[reply]