HTML code help

scottalanmiller

@technobabble

Wonder if that was more a Ballmer thing (the guy of the "I will f@cking destroy those guys" fame)

Considering Netscape wasn't good enough so they made IE
Java wasn't good enough, so j#
C/C++ wasn't good enough, so C#
Flash wasn't good enough, so Silverlight

Not that they weren't good enough, they just weren't proprietary. It was all an attempt to move people to Microsoft platforms.

scottalanmiller

Can't forget... they didn't want to use JavaScipt so they made JScript.

technobabble

Too true and although there are many MS things along the way I have liked, most of what you mentioned was wasted time on programming much like Office Accounting. MS giveth and MS taketh away. Look for my upcoming RANTs on MS OneNote and Outlook 365.

scottalanmiller

J++ was the original replacement to Java. It was just a really crappy version of Java. I had a Visual J++ kit once up on a time.

J++ was replaced by J# in 2004 which kept the Java syntax but switched from Java VM underneath to the .NET system. Making it "easy" for Java people to move over to the .NET world.

But that too was discontinued in 2006 as C# itself was always a Java replacement, not targeted at C/C++ but at Java. Java is a C derivative in syntax as is C#, so in a way it's all C, sort of, but conceptually Java and .NET are pretty far removed. C# goes after Java though, not C. Microsoft maintains Visual C++ as their C/C++ replacement.

scottalanmiller

@technobabble said:

Look for my upcoming RANTs on MS OneNote and Outlook 365.

Office 365?

technobabble

LOL...I should have said the Office 365 Outlook browser web app.

scottalanmiller

@technobabble said:

LOL...I should have said the Office 365 Outlook browser web app.

Oh, that's just normal OWA.

technobabble

But it opens different than straight OWA.

scottalanmiller

@technobabble said:

But it opens different than straight OWA.

In what way? Are you comparing it to the latest OWA from Exchange 2013?

technobabble

Ah...that might explain your comment. About 4 months ago one of my clients OWA was from Comcast and it didn't look the same, so I presume they weren't using 2013 Exchange.

scottalanmiller

@technobabble said:

Ah...that might explain your comment. About 4 months ago one of my clients OWA was from Comcast and it didn't look the same, so I presume they weren't using 2013 Exchange.

OWA 2013 is definitely much different than any of the OWAs in 2010.