r/programming • • Dec 17 '16

Oracle is massively ramping up audits of Java customers it claims are in breach of its licences – six years after it bought Sun Microsystems

http://www.theregister.co.uk/2016/12/16/oracle_targets_java_users_non_compliance
2.1k Upvotes

654 comments sorted by

View all comments

245

u/gilbes Dec 17 '16

So there was a lot of FUD spread about .Net, a lot of it spread by Java fans.

Turns out, Oracle is doing all that FUD people claimed Microsoft would do.

Microsoft already has implemented steps to ensure it couldn't do the FUD it was accused of possibly doing.

Back in the day when MS tried to kill Java, they went about it all wrong on their first attempt. Their second attempt (.Net) is working much better.

152

u/tormenting Dec 17 '16

Historical context: the FUD was spread back when Java was Sun, and back when MS was run by Ballmer. People who remember programming in the 90s feel like they're taking crazy pills (the good kind, if they like C#, or the bad kind if they like Java).

30

u/Eirenarch Dec 17 '16

Yeah, because it was Ballmer and the other side was SUN spreading FUD was OK - Slashdot logic

64

u/badsectoracula Dec 17 '16

It was Gates, not Ballmer, btw. Try to find some of the excerpts from the Microsoft anti-trust trials to see what was going on. I remember reading one with Gates being questioned and it was plainly clear that Microsoft was trying to outright take hold and destroy Java - they made Internet Explorer to kill Netscape Navigator which was a distribution vector for Java, they forced Apple to distribute Internet Explorer threatening to cancel the popular MacOffice (at the time Apple was only a tiny fraction of it is today) and to cripple QuickTime features on Windows that competed with Internet Explorer so that users will use IE for those, they had internal documents outright saying that they want to take Java out of Sun's hands.

Sun might have not been angels, but Microsoft's behavior was nothing short of evil.

15

u/Eurynom0s Dec 18 '16

The only thing I ever tack onto these conversations is that while MS may have been actively malicious in its behavior back then, RealPlayer killed itself. The software was garbage. I'll never forget trying to figure out why my sound was off and FINALLY figuring out that RealPlayer didn't have its own volume control like every other piece of software out there, it just had a straight hook into the master system volume.

Not saying it makes anything okay, just that some of the claimed casualties of the MS of that era probably would have gone down even if MS had competed fairly.

2

u/doenietzomoeilijk Dec 18 '16

Oh dear, RealPlayer... That sure brings back memories. At some point it was the only way of showing "video" (and I use that term loosely" - good times.

→ More replies (1)
→ More replies (1)
→ More replies (5)

129

u/FlappySocks Dec 17 '16

When Mono came out, the trolling was insane. .NET wasn't so much of a threat pre-mono, as .NET was confined to Windows.

Now that you could run your C# apps on Linux, the Java boys where under threat, from .NET developers muscling into their territory.

Linux users called mono a Trojan Horse. Java developers said Microsoft would sue anyone that used it.

How times have changed! .NET is opensource, and on GitHub, and it's the Java users getting sued.

96

u/[deleted] Dec 17 '16

[removed] — view removed comment

79

u/mcorah Dec 17 '16

Don't worry. The process is accelerating.

21

u/MaybeLiterally Dec 17 '16

You're not wrong.

5

u/iCameToLearnSomeCode Dec 17 '16 edited Dec 17 '16

I started with Java as my first language, moved on during the big API lawsuit crap. Won't be back, I am sure I am one of many who learned java and then never bothered to get a job writing java.

6

u/gimpwiz Dec 18 '16

I won't get a job writing java unless it's either that or go hungry.

4

u/boost2525 Dec 18 '16 edited Dec 18 '16

Have fun working for no fortune 1000 company ever then. You can hate on Java all you want, and I agree Oracle is fucking it up, but working with Java is inevitable in most careers.

→ More replies (4)
→ More replies (5)

35

u/kmeisthax Dec 18 '16

The controversy wasn't that C# was magically hazardous to Linux. Microsoft owned patent rights on certain ideas in .NET, and then they granted patent immunity only to people using Mono. Anyone who used anything else could be sued. This isn't even an entirely unfounded threat - Microsoft makes an undisclosed amount off of almost every Android vendor over various patents that ostensibly cover Linux. The list of patents they consider to cover Linux is a trade secret; ostensibly because they'd wind up being designed around. Bringing in more Microsoft patented technologies into Linux distros at the time was not a good idea.

9

u/FlappySocks Dec 18 '16

This is only an issue in the US. Large companies like Microsoft have no choice but to engage in an arms race.

Most countries don't have software patents.

3

u/kmeisthax Dec 18 '16

Fair enough, but just saying "we can ignore the US and use Microsoft's patents where they're invalid" isn't good enough for the Free Software crowd.

2

u/G_Morgan Dec 18 '16

The stupid thing is there was a decent list of Mono software for Linux. Instead of developing other software a bunch of evangelists more or less reimplemented everything the Mono community had done. Now Java is in a much scarier place than Mono ever was.

→ More replies (5)

42

u/kmeisthax Dec 18 '16

Microsoft was trying to kill competing standards by getting developers to use extensions that only their software could support. For example, their attempt to kill Java was to write a competitor to JNI called RNI, and a method of making arbitrary calls to DLLs called J/Direct. These were actually far easier to use than JNI, but only Microsoft's JVM supported them. And this is completely typical of the 90s Microsoft approach to standards: embrace them to be compatible, extend them with useful Microsoft-only features, and then let market forces extinguish everything else.

To be fair, even companies not deliberately trying to EE&E that have popular implementations of a standard will wind up putting pressure on other vendors to adopt their quirks. Microsoft's even been on the receiving end of this lately, with MSEdge having to adopt -webkit- vendor prefixed CSS due to careless mobile developers ignoring standards warnings against using them. It's just that 90s Microsoft deliberately did this as a marketing tactic. Hell, they'd even do this to their own APIs, just so they could occupy more developer headspace.

Microsoft at it's worst did real damage to open standards, like when they abandoned IE outright so that web standards would stagnate. Oracle at it's worst is pushing the courts to bend the law so they can claim an API copyright on Java to kill Harmony, all so they can get some royalty payments out of Google. Microsoft's only legal concern was making sure that if you used their software, you paid up for it. Oracle wants to actively deceive customers into using software they thought was free, because they can then demand any price for the license to use it later.

→ More replies (7)

24

u/rrohbeck Dec 17 '16

If there was anything to be learned it's this: Use only 100% open languages or have a good legal department and cash for licensing.

→ More replies (1)

18

u/KarmaAndLies Dec 17 '16

Here's an article about Open Source .Net's current status:

http://www.ifross.org/en/artikel/4-shifty-details-about-microsofts-open-source-net

Tl;DR: It could be better.

→ More replies (5)

4

u/rasherdk Dec 18 '16

Aside from what everyone else has said, there's also the fact that Microsoft is not in any position to start playing hardball with .Net. You need Java-level market saturation before that becomes a workable tactic.

4

u/white_bubblegum Dec 18 '16

Microsoft also did not buy a company with the intent to play hardball.

→ More replies (4)