Announcing Azure Command-Line Interface 2.0 Preview

Re:Announcing Azure Command-Line Interface 2.0 Preview by mhuffman on Tuesday September 27, 2016 @06:16PM (#12593684)

Oh boy did you miss something in the 90s! It was call active pages (or some bullshit, I have tried to block it from my memory) and it made Internet Explorer the king of browsers and still locks in a lot of government agencies and business from upgrading their infrastructure, because they don't want to lose or have to pay to redevelop "critical" applications to their daily work.

[ Parent | on HN ]

Re:Announcing Azure Command-Line Interface 2.0 Preview by cbhl on Tuesday September 27, 2016 @06:32PM (#12593776)

ActiveX?

https://en.wikipedia.org/wiki/ActiveX

[ Parent | on HN ]

Re:Announcing Azure Command-Line Interface 2.0 Preview by programmer_man on Tuesday September 27, 2016 @07:49PM (#12594303)

No, this: https://en.wikipedia.org/wiki/Active_Desktop

Kind of related, it was a COM control you could stretch over your whole desktop, that received push notifications.

Also, I believe it was TOTALLY secure.

Edit: Dang it, I missed where they said "and it made ie the king of browsers." -- Yes, ActiveX

[ Parent | on HN ]

Re:Announcing Azure Command-Line Interface 2.0 Preview by cbhl on Thursday September 29, 2016 @02:16PM (#12607529)

I was 8 when Active Desktop came out -- I used it to put Neopets on the desktop of my computer.

[ Parent | on HN ]

Re:Announcing Azure Command-Line Interface 2.0 Preview by girvo on Tuesday September 27, 2016 @07:46PM (#12594288)

I think they mean Active Server Pages, ie. classical ASP, which you could program using Visual Basic?

[ Parent | on HN ]

Re:Announcing Azure Command-Line Interface 2.0 Preview by int_19h on Tuesday September 27, 2016 @08:39PM (#12594547)

ASP was programmed using VBScript (and actually extensible - it used Active Scripting, so you could also do JS, and third parties added support for e.g. Perl). And, since it was server-side tech, and very low-level at that, it didn't care what browser rendered the output.

I think this was a reference to ActiveX. Although most ActiveX controls weren't written in VB, either, even though you could do it - the resulting control was just too large to download, because you had to include ~2 Mb of VB runtime (remember, we're talking about the time back when dialup was still incredibly common - and 2 Mb takes 5 minutes to download on 56k). Mostly it was done in VC++ with ATL.

[ Parent | on HN ]