Advanced

Leaving .net

Posted by mbaehrlxer on · 1 comment
whatupdave.tumblr.com; By Dave Newman 		Mail this story
Print this story

The endless rebuilding of data mappers, logging code, object resolution mechanisms, messaging systems and web frameworks adds up to a massive waste of time, effort and potential. I’m not talking about public collaborative efforts, I’m talking about in house “Not invented here” syndrome. This is what happens when you have a community cut off from the world. A community that doesn’t talk to each other and work together. This is what the .net community is.

Full Story

  Nav
» Read more about: Story Type: Editorial; Groups: Community

» Get new stories by e-mail: nightly or as they are published

« Return to the newswire homepage

Comments (1)

phsolide ·
The key point that this article raises is somewhat buried:
Quoting: stymied by Microsoft themselves who are so cleverly changing just fast enough to keep developers from solving problems themselves.
The "just fast enough" part is important, and not a mistake or just bad luck or due to some random combination of circumstances.

Microsoft wants the developers to not solve problems for themselves, otherwise, Microsoft would have nothing to sell them. Stable APIs doom proprietary solutions, at least in a large community.

Post a comment

A free account is needed to post. Write your comment here first: your text is kept in this browser while you sign up or log in, and is waiting for you when you come back.

Your message:
|||||
10
Markdown: **bold**, *italic*, [text](https://link), - lists, > quotes, $x^2$ for math. Formatting help

Sign up and post (it is free)  or  Log in and post