Friday, March 6, 2015

Some comments censored by Microsoft on March 6, 2015 !

Rautare commented  ·  March 6, 2015 9:37 PM
VB6 will out-last that entire .NET generation of tools: a comment by Anonymous:

Derbedeu commented  ·  March 6, 2015 9:28 PM  ·
Andrew Clarke says

The crash of the TradElect trading system on the London, and Johannesburg, Stock Exchange for seven hours was a disaster that probably led to the loss of around £3bn in trading.

Microsoft described the application as being ‘One hundred per cent reliable on high-volume trading days’

The system promised to give sub-ten millisecond response times, rather than 7 hour response times.

The whole incident has been a major embarrassment for Microsoft since they made so much of the reliability of the system.

Derbedeu commented  ·  March 6, 2015 9:27 PM  ·
TradElect was the London Stock Exchange's main electronic trading platform from 2007 to 2011. It ran on Microsoft Windows, using .NET technology and Microsoft SQL Server. Its development took 4 years from project inception to rollout and had a total cost of £40m.[1]

... no comment

Derbedeu commented  ·  March 6, 2015 9:27 PM  ·
"No one in his right mind will choose VB6 to design a business software today."

I made a VB6 app last month for CERN !

"This is the common problem with conservative VB6 users"

it looks like you're s t u p i d again and that you easily forget what everyone said here: We, the Visual Basic 6.0 prograsmmers know and work with most programming languages. That is the main reason for which we are able to say that .Net is a loss of our time.

If you do not bring back VB6, you will become increasingly insignificant ...

Derbedeu commented  ·  March 6, 2015 9:26 PM  ·
Andrew Oliver says

Why Microsoft .Net failed...

Microsoft tried, but it couldn't win the hearts and minds of developers who weren't already indoctrinated -- and it alienated others along the way.

Like many Microsoft "innovations," .Net was a copy (embrace) and improvement (extend) of someone else's technology -- in this case, Java.

Unfortunately, .Net also cannibalized Microsoft's most successful corporate IT development environment, Visual Basic.

Visual Basic .Net didn't have much to recommend it. There wasn't enough documentation, so you had to learn C# anyhow.

Instead of .Net propping up Windows, the greater Windows ecosystem propped up .Net. People coded to .Net because they were coding for SharePoint or BizTalk. If you delve deep into .Net jobs, you'll notice they tend to be legacy or related to SharePoint and friends.

Now it's too late for .Net. As we move from IaaS to PaaS and SaaS, folks are simply unlikely to care about operating systems. If you don't care about operating systems, why not code as if you don't care about operating systems and code for the cloud? We've seen recently that Azure isn't lighting the world on fire. Why would we expect that to change?

This results in a downward spiral for 'Softies hoping that writing to .Net is enough.

Derbedeu commented  ·  March 6, 2015 9:25 PM  ·

"Look at the 15 languages I have listed below. "

Look at the comments listed below that list. Lists like this will put Microsoft in total obscurity and irrelevance if VB6 is not back !


Anonymous commented  ·  March 6, 2015 9:19 PM  ·
I look at youtube and it is filled with Visual Basic 6 tutorials. Many rankings put VB6 on the first place:

No comments:

Post a Comment