5 ms·

> the massive dissonance between the experience of professional programmers and what really appears to be an endless throng of chipper hobbyists who are excite

> the massive dissonance between the experience of professional programmers and what really appears to be an endless throng of chipper hobbyists who are excited to "follow the ride" of this thing through clumsy (but Open, yay!) development. Do you think hobbyists would really waste their time with Linux and Command Line tools when they can just download Visual Studio on Windows ? You seem to misunderstand why asp.net chose to go open source at first place. > You get the impression that people at Microsoft are being rewarded for the number of issues being raised on GitHub for a not-ready-for-prime-time technology ecosystem, in the guise of "building a community." It's... odd. They basically had to rewrite the entire framework + .net to run it on Linux. I'm pretty sure they are working quite hard and not wasting their time on Github social gimmicks to try to deliver the product in time. Why are you so angry against MS ? Because they break stuff? they always did that. Except now it's open source so if you don't like where it is going you can fork it.

tacos 10y ago
Look at the way they're approaching Bash on Windows (which was also defended by shanselman in that thread). This is a brain dead, check-off-the-boxes compatibility exercise. Instead they threw some half-baked crap on Github and said "Hey community, let us know what doesn't work!" They pulled the same nonsense with C99 support. I know it's dark and rainy and lonely in your office, but just do the work, m'kay? Instead they got Redis limping on it and so decided to release everything as part of an extended tradeshow demo. But months later they realized that it can't handle files that end in a period -- after the community alerted them. This is an absurd way to approach building a critical compatibility layer. It's a waste of everyone's time. But they're over-excited about community input now. They said they were listening with Windows 8, too -- and now Sinofsky's new career is writing LinkedIn articles all day, pretending he didn't drive a $100 billion ecosystem into the ground for three years. Likewise does the OneDrive team really need a UserVoice site to tell them the thing simply doesn't work? A terabyte an hour of error logs and telemetry isn't enough I guess.
- deleted 10y ago
  [deleted]

tacos 10y ago

Look at the way they're approaching Bash on Windows (which was also defended by shanselman in that thread). This is a brain dead, check-off-the-boxes compatibility exercise. Instead they threw some half-baked crap on Github and said "Hey community, let us know what doesn't work!" They pulled the same nonsense with C99 support. I know it's dark and rainy and lonely in your office, but just do the work, m'kay? Instead they got Redis limping on it and so decided to release everything as part of an extended tradeshow demo. But months later they realized that it can't handle files that end in a period -- after the community alerted them. This is an absurd way to approach building a critical compatibility layer. It's a waste of everyone's time. But they're over-excited about community input now. They said they were listening with Windows 8, too -- and now Sinofsky's new career is writing LinkedIn articles all day, pretending he didn't drive a $100 billion ecosystem into the ground for three years. Likewise does the OneDrive team really need a UserVoice site to tell them the thing simply doesn't work? A terabyte an hour of error logs and telemetry isn't enough I guess.

deleted 10y ago
[deleted]