Hacker News new | ask | show | jobs
by TheRealDunkirk 3477 days ago
No, they're not different from anyone else for having a profit motive, but Microsoft, on the other hand, had a very long stretch of using underhanded and illegal tactics to stifle competition. I would argue that they're STILL abusing their monopoly position on the desktop. THAT is what makes them different than the rest, and that, to me, is what tempers my attitude about these recent announcements.

Another difference is that the other examples you've listed here are all free software. Of all the glowing coverage Microsoft has been getting of late, only .NET on Linux is comparable. But you're never going to get Windows-forms-like applications on Windows (which a surprising number of people seem to think will happen). It's only the web stack. Does ASP.NET really stack up well against Rails or Node.js as a web application stack on Linux? I don't know, but at the least, they have some catching up to do.

But, really, I think it's another example of my main point. Microsoft could have used some pre-existing open source project and built on top of that, but they chose to create another language for the future. It's even pretty good, by all accounts. It's just that, in a world of PHP, Javascript, C++, Ruby, Python, Erlang, and all the rest, what place does a closed-source language and compiler have? They had to make it open source.
2 comments
benaadams 3477 days ago
> Does ASP.NET really stack up well against Rails or Node.js as a web application stack on Linux?

Yes; have a look at the language column one this page:

https://www.techempower.com/benchmarks/#section=data-r13&hw=...

link
TheRealDunkirk 3476 days ago
I wasn't thinking about speed benchmarks. I was referring to the whole "ecosystem" of the work, from language to plugins to the editors commonly used to community activity around it, etc.
link
quanticle 3477 days ago
But you're never going to get Windows-forms-like applications on Windows

You absolutely will be able to get Windows-forms like applications. You just won't be using WinForms or WPF. Instead, you'll use Mono and its bindings to GTK or QT. This is exactly how it should be. WPF is an OS specific GUI library. Using WPF on Linux makes about as much sense as using Cocoa on Windows.

But, really, I think it's another example of my main point. Microsoft could have used some pre-existing open source project and built on top of that, but they chose to create another language for the future.

I think you're misremembering history. C# was created because Sun specifically cut Microsoft off from using Java. Microsoft had a project to write its own Java compiler. Sun took legal action to prevent Microsoft from doing so. And this was during the early 2000s. Python, Ruby, etc. were nowhere near mature enough to serve as the primary systems programming language for something like Windows.

Moreover, Microsoft gets a lot of criticism for making C#, but Google gets no criticism for making Go? Isn't that just slightly hypocritical?

link
blub 3476 days ago
Sun cut off MS from Java because MS was creating an incompatible version of Java. That's the extend step.
link
prodigal_erik 3475 days ago
They were not only dropping standard features like RMI and JNI but also sneaking proprietary methods into standard classes. They could have clearly and honestly put them in a com.microsoft package, but they couldn't trick anyone into writing unportable code that way, so they forked the whole language instead of contributing anything.
link
TheRealDunkirk 3476 days ago
> Instead, you'll use Mono and its bindings to GTK or QT. This is exactly how it should be.

Oh, I'm quite clear. My point is that, if the stack had delivered on the premise of the idea of WinForms-level-easy GUI development, why haven't Mono-based GUI apps proliferated on Linux? Yet, after many years of including Mono in Ubuntu, they've pulled it from the default install.

> Microsoft had a project to write its own Java compiler. Sun took legal action to prevent Microsoft from doing so. And this was during the early 2000s. Python, Ruby, etc. were nowhere near mature enough to serve as the primary systems programming language for something like Windows.

Fair enough, but even all the way back in 2000, it was obvious that, if you were going to start from scratch on a language, there was no point in making it closed. There wasn't any more real money to be made in compilers by that point. GCC was being made available on everything, and $1,000 proprietary compilers were dying out.

> Isn't that just slightly hypocritical?

Sigh.

link