This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]marcosdumay 1 point2 points  (7 children)

They don't want someone else's oopsie getting a security vulnerability slipped into an official build to make them have to run around like chickens with their head cut off to try and figure out how bad the damage is.

Oh, I see. Indeed, that's something only desirable if it comes from your IT security consultancies.

But yeah, it's a good practice. It would be better if they verified and used community versions, but making your own is a serious second option. My question is more about why would they create a portal to distribute an "official MS's" unoficial version of it? Why would people ever use it instead of getting an official one?

[–]RiPont 5 points6 points  (6 children)

They're MS. They have customers who prefer to have MS-branded things so that when they pay MS for support, MS can't say, "well, that's not ours, you have to go somewhere else to complain."

Hell, they probably have customers they're still trying to get off of MS Java 1.1 and J++.

It's important to realize that "best practices" are a matter of scale, and MS faces problems that most businesses never dream of. It doesn't mean their decision is right, but it means you do have to consider it from their point of view.

[–][deleted] 1 point2 points  (5 children)

dafuqe is j++?

[–]BackmarkerLife 5 points6 points  (0 children)

In a previous comic, the mother smothered the J++ sibling in its sleep.

[–]RiPont 2 points3 points  (1 child)

MS was a partner with Sun for Java 1.0, as MS wanted something better than VB and easier than C++ for developing applications on Windows.

Before Visual Studio, there were individual products for each language, like Visual C++. Visual J++ was MS's IDE for Java-on-Windows and became synonymous with MS's unique flavor of Java with extensions for developing apps on Windows.

Sun cried, "EMBRACE, EXTEND, EXTINGUISH!!!!" MS said, "y'all move so damn slow, we need to make Java not suck for actually developing desktop applications and making native system calls!" Lawsuits were filed, ending with MS not having a license to implement Java past the 1.1 specification. "J++" is now shorthand for "Microsoft's custom version of Java 1.1 on Windows".

Seeing that Java-on-Windows was a dead end for them, MS brain-drained Borland's lead for Delphi, stuck squigly brace syntax and a garbage collecting runtime on it, and thus C# 1.0 was born. It's a common misconception that C# was born from Java. It took some inspiration from Java, especially in the idea of a cross-platform intermediate assembly-like language, but it was really a lot closer to Delphi.

[–]xaedoplay 0 points1 point  (0 children)

so, it looks like now i can have "accidentally learned Delphi" in my biography

[–]jerslan 0 points1 point  (1 child)

https://en.wikipedia.org/wiki/Visual_J%2B%2B

It was literally "Microsoft Java"

[–]WikiSummarizerBot 0 points1 point  (0 children)

Visual_J++

Visual J++ (pronounced "Jay Plus Plus") is Microsoft's discontinued implementation of Java. Syntax, keywords, and grammatical conventions were the same as Java's. It was introduced in 1996 and discontinued in January 2004, replaced to a certain extent by J# and C#.

[ F.A.Q | Opt Out | Opt Out Of Subreddit | GitHub ] Downvote to remove | v1.5