Linked by Thom Holwerda on Tue 18th Dec 2012 00:03 UTC
Microsoft Microsoft has just responded to Google's move regarding Exchange ActiveSync. Sadly, instead of addressing the very real problems consumers are about to face, Microsoft starts talking about switching to Outlook.com.
Thread beginning with comment 545640
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Comment by shmerl
by lucas_maximus on Tue 18th Dec 2012 13:00 UTC in reply to "RE[2]: Comment by shmerl"
lucas_maximus
Member since:
2009-08-18

I can't speak about ASP.NET specifically,


Well they aren't the same thing then are they?

but the .NET is only just open enough to make some .NET applications barely run. However closed so much that applications are buggy or even unusable because of major features being unavailable.


What are you on about?

One great example of this is the DRM extensions; and thus the reason why Netflix, Lovefilm and so on cannot run on Linux (albeit not without running native Windows libraries on WINE).


Again, I dunno what this has to do with parts of ASP.NET being Open sourced.

What's more, .NET was invented because MS couldn't play ball with Java (see below).


So?

OOXML was written because MS wanted to lock people into MS Office but were forced to use an open standard by the EU.

If Microsoft really cared about open standards, they'd have used ODF like nearly every one of their competitors do. Instead, they create their own incompatible standard that nobody else uses but them.


Well the de-facto standard is MS Office, so any competitor that wants to be able to read the same files need to support that or get out of the market.

Sun trying to make people use ODF was a silly move.

C# is another example of MS creating a new standard to trash an existing standard. In this case .NET was invented to trash Java (though C# / .NET has evolved since).


C# version 1.0 was a superior language to Java, Properties alone in the language make it vastly superior as well as the better designed DateTime libraries (two things I can think of off the top of my head).

C# is Java Improved.

What's more, .NET was only developed after MS got sued by Sun for releasing their own incompatible Java run times.


One thing so far is true at least.

If MS cared about standards, they'd have released a Sun Java compatible IDE like Borland had.


Borland Java IDEs were crap, thank goodness they didn't

Please do, because every one of your examples demonstrates how MS had shunned established standards ;)


What established standards? A Document standard on an Office suite with a quite a small user base and a programming language developed by the same people that wanted the said document standards.

Firefox 1 & 2 were significantly more standard compliant than IE. Plus there was Opera, and kHTML-based browsers (even webkit was released in 98, a year before you claimed the competition began)


KHTML and Opera have always had low market share and aren't significant enough to be relevant to the
conversation.

Firefox 1 was more standards compliant than IE6 because it was newer. What the OP always misses is that the reason people moved to it was nothing to do with standards compliance and the fact that at the time it was a better browser with more features.

2009 was when IE8 got released and was the first browser to support CSS 2.1 and XHTML 1.1 properly (I am sure you bring up Opera, but I don't see them as a serious competitor to the other browsers in Market share).

Edited 2012-12-18 13:04 UTC

Reply Parent Score: 1

RE[4]: Comment by shmerl
by Laurence on Tue 18th Dec 2012 13:40 in reply to "RE[3]: Comment by shmerl"
Laurence Member since:
2007-03-26

I see you've resorted to the "if you can't counter argument, then change the argument" method of trolling the interwebs.

Well the de-facto standard is MS Office, so any competitor that wants to be able to read the same files need to support that or get out of the market.

You're now moving the goal posts as 'de facto standard' isn't the same as 'open standard'. You were arguing about open standards.


Sun trying to make people use ODF was a silly move.

...and Google, IBM, KDE and plenty others I can't be bothered to list: http://en.wikipedia.org/wiki/OpenDocument#Application_support

ODF support was one second to MS's own proprietary formats. So if Microsoft cared about open standards, then they'd have switched to an established and widely supported format instead of creating their own one from scratch.

C# version 1.0 was a superior language to Java, Properties alone in the language make it vastly superior as well as the better designed DateTime libraries (two things I can think of off the top of my head).

Weird, I seem to recall that .NET v1 stank (and back then I was 100% a Windows user and developer). Though I'll grant you that things have improved massively over the years. I quite enjoy using .NET these days.

However technical merits of C# aside, we're talking about open standards. C# was invented to break established standards.

Borland Java IDEs were crap, thank goodness they didn't

You're obviously too young to remember what life was like before MS's monopoly. Borland's IDEs used to be second to none. It's 'only' in 10 / 15 years that MS had overtaken Borland.

However that's besides the point as you're now arguing about the quality of the IDE, which absolutely nothing to do with the open standards of languages.

What established standards? A Document standard on an Office suite with a quite a small user base and a programming language developed by the same people that wanted the said document standards.

I guess if you've only ever used MS technology then you're bound to be ignorant to the rest of the IT industry and their established standards ;)

KHTML and Opera have always had low market share and aren't significant enough to be relevant to the conversation.

You're hardly one to comment on the relevance of example given the number of times you've changed the argument to suit your bias.

Firefox 1 was more standards compliant than IE6 because it was newer.

Even IE7 lacked backed standards features that FF1 supported.


2009 was when IE8 got released and was the first browser to support CSS 2.1 and XHTML 1.1 properly (I am sure you bring up Opera, but I don't see them as a serious competitor to the other browsers in Market share).

when talking about standard compliance, you can't just exclude figures that disprove your point, simply because of market share. That's just a whole new level of narrow-mindedness.

What's more, you're just picking two arbitrary specifications chosen specifically because IE happened get there first. However when you look at the overall performance (eg using ACID as a benchmark), you'll see that IE was consistently one of the last browsers to meet standards (and that's even excluding Opera!)

Reply Parent Score: 10

RE[5]: Comment by shmerl
by lucas_maximus on Tue 18th Dec 2012 14:47 in reply to "RE[4]: Comment by shmerl"
lucas_maximus Member since:
2009-08-18

You're now moving the goal posts as 'de facto standard' isn't the same as 'open standard'. You were arguing about open standards.


TBH I don't really care one way or another. I do care about people complaining about Microsoft supporting something that nobody uses and doesn't benefit their customers.

...and Google, IBM, KDE and plenty others I can't be bothered to list: http://en.wikipedia.org/wiki/OpenDocument#Application_support


And? So you have the most popular document format in the world and they make their own competeting standard and it didn't work out well.

Why would Microsoft support such as move, I don't know.

If I made my own popular file format and someone told me I should support it and it isn't nearly as widely used, I wouldn't bother to support it either.

ODF support was one second to MS's own proprietary formats. So if Microsoft cared about open standards, then they'd have switched to an established and widely supported format instead of creating their own one from scratch.


Why would they do that? there is no motivation to do so.


Weird, I seem to recall that .NET v1 stank (and back then I was 100% a Windows user and developer). Though I'll grant you that things have improved massively over the years. I quite enjoy using .NET these days.


YES .NET 1.0 and 1.1 weren't great. C# != .NET.

However technical merits of C# aside, we're talking about open standards. C# was invented to break established standards.


How can something be invented to break standards? It doesn't make sense.

It like saying I am inventing PHP to break Python.

You're obviously too young to remember what life was like before MS's monopoly. Borland's IDEs used to be second to none. It's 'only' in 10 / 15 years that MS had overtaken Borland.


Their Java IDE was still rubbish.

However that's besides the point as you're now arguing about the quality of the IDE, which absolutely nothing to do with the open standards of languages.


I was just stating my preference.

I guess if you've only ever used MS technology then you're bound to be ignorant to the rest of the IT industry and their established standards ;)


There was nothing that was a dejure standard that everyone used.

You're hardly one to comment on the relevance of example given the number of times you've changed the argument to suit your bias.


To be honest I went down this road because of ASP.NET being open sourced recently.

TBH I don't really care about the rest.

Even IE7 lacked backed standards features that FF1 supported.


Yes IE7 was rubbish and had no excuse to be.

2009 was when IE8 got released and was the f
when talking about standard compliance, you can't just exclude figures that disprove your point, simply because of market share. That's just a whole new level of narrow-mindedness.


Well this is what a lot of developers are currently doing on Mobile. Webkit is king and anything that isn't Webkit is a second class citizen. Like it or Lump it that the way it is.

IE8 for CSS and XHTML was fine, If you whine about SVG and other things ... these simply aren't used by web developers.

What's more, you're just picking two arbitrary specifications chosen specifically because IE happened get there first. However when you look at the overall performance (eg using ACID as a benchmark), you'll see that IE was consistently one of the last browsers to meet standards (and that's even excluding Opera!)


Two arbitary specifications!! Only the most important 2.

Because I rate my browsing experience on whether something can pass the ACID test.

Reply Parent Score: 0

RE[5]: Comment by shmerl
by sukru on Tue 18th Dec 2012 14:57 in reply to "RE[4]: Comment by shmerl"
sukru Member since:
2006-11-19

I'll just jump in for the C# part. This is because I like the guy who did it (Anders Hejlsberg, who also gave us Turbo Pascal and Delphi before).


"C# version 1.0 was a superior language to Java, Properties alone in the language make it vastly superior as well as the better designed DateTime libraries (two things I can think of off the top of my head).

Weird, I seem to recall that .NET v1 stank (and back then I was 100% a Windows user and developer). Though I'll grant you that things have improved massively over the years. I quite enjoy using .NET these days.
"

I remember reading "C# for Java Developers" when I was in college. I don't remember being impressed by many books on the technical level as much as I did with that one. Every decision they made was for fixing the problems I had with java (no signed integers, no easy way to talk native, no easy xml processing, and of course properties, and metadata).

C# was only built, because MS could not adopt Java for Windows development (as you said they were sued for J++). But they only reason they wanted to extend Java was they knew (Anders knew) Visual Basic did not have any future (i.e.: pretty much sucked), and Java was the best thing out there. But there were the issues with Java on the desktop front - which they fixed with C#, so they had to extend it. Even today, except for Eclipse framework, the standard Java GUI APIs are real bad compared to C#/XAML.

Were Java an open standard at that time, Sun could not have sued for J++, and we would have a Windows dialect of Java, which would probably be backported to the main standard by open source hobbyists. But since Java was never an open standard (until maybe C# got pretty big), they closed it down from MS's use.


However technical merits of C# aside, we're talking about open standards. C# was invented to break established standards.


As I said, Java was not an open standard (still not an ISO/ECMA standard AFAIK).


"Borland Java IDEs were crap, thank goodness they didn't


You're obviously too young to remember what life was like before MS's monopoly. Borland's IDEs used to be second to none. It's 'only' in 10 / 15 years that MS had overtaken Borland.
"

Again the Anders factor here. Borland was good, while he was at the helm. They went down when he left, and they did not know what to do. I remember trying to use their express editions to come back, but they would not let two different versions (e.g.: C++, and C#) at the same. Then they stopped distributing free starter versions all together. Now look at the size of Delphi developers, and I feel real sad (I started actual programming with Turbo Pascal back in the day).

Reply Parent Score: 5

RE[5]: Comment by shmerl
by ze_jerkface on Fri 21st Dec 2012 09:03 in reply to "RE[4]: Comment by shmerl"
ze_jerkface Member since:
2012-06-22

However technical merits of C# aside, we're talking about open standards. C# was invented to break established standards.


Java was never an established standard. It would be easier to argue that Java was invented to break established C++ standards.

But the real problem is that C++ was created to break ASM standards. And don't even get me started on what happened to the abacus.

Edited 2012-12-21 09:04 UTC

Reply Parent Score: 2

RE[4]: Comment by shmerl
by JAlexoid on Fri 21st Dec 2012 00:52 in reply to "RE[3]: Comment by shmerl"
JAlexoid Member since:
2009-05-19

Well the de-facto standard is MS Office, so any competitor that wants to be able to read the same files need to support that or get out of the market.

Sun trying to make people use ODF was a silly move


It may have been a silly move, but it was to break single vendor lock in. Which OOXML was countering, and successfully countered. Result? Single vendor lock in!

Reply Parent Score: 2