Plots End Visual Basic

• by JaredOfEuropa( 526365 )

  That would suck, C# is actually kind of decent. What would they replace it with, some kind of mongrel version of Python (P#)?

  • by Dutch Gun( 899105 )

    C# isn't going away anytime soon. It's pretty clear MS is doubling-down on C#, especially given their continued focus on making.NET core both open source and portable to other OSes like Mac and Linux. And C# is the defacto language of.NET programming.

    Incidentally, there was already a.NET version of Python called IronPython. I think it sort of got left behind in the version2/3 split, though.

    • by AmiMoJo( 196126 )

      C# almost makes VB redundant anyway. It's so easy there really isn't much of a gap between it and VB, so it doesn't make much sense to keep maintaining VB.

      Also VB is help back by the language syntax and limited flow control options. Microsoft tired to hack in more C# like stuff but there is only so far they can take it. A lot of the benefits of recent.NET and Core releases are unavailable in VB because of this.

  • by UperPoti( 832091 )

    What is popular and a turd? Basic -> VB; C(++) ->C#; JavaScript -> TypeScript = Electron Everything! (MS Teams)
  • 1 reply beneath your current threshold.
• • • by gbjbaanb( 229885 )

      .NET core is cross platform. I run a website written in C# on Centos right now, it even uses a SQL Server running on the same linux server.

      It does mean there's really no reason whatsoever to keep running Java though.

  • 2 replies beneath your current threshold.
• • by Anonymous Coward

    C# is one of the most popular development languages and.NET is right up there with Java as one of the best development runtimes, each has advantages with neither clearly better than the other.

    The same could have been said about Visual Basic back when VB 6.0 first came out. It was a very popular and highly active community of developers. Then Microsoft left Visual Basic to stagnant and wither as they pursued Visual J++ and.NET efforts. It took a long time before VB.NET came about, and even when it did, it was totally incompatible with old VB6 source code.

    Mark my words, C# will suffer the same fate. As soon as Microsoft gets excited about something else, it will leave C# far behind, and all those

• by transporter_ii( 986545 )

  Yeah, sometimes I feel sorry for people that don't want to learn new things. But then, sometimes I don't either. I knew a guy that wouldn't move past Classic ASP. And I knew a guy that wouldn't move past VB 6. I sometimes laugh at all the code they had to write, when I can produce the exact same result in a couple of lines or so of code.

  But again, sometimes I don't want to learn new things, either.

  • by Anachronous Coward( 6177134 )

    But again, sometimes I don't want to learn new things, either.

    I hate learning. But I do enjoy knowing.

• by Humbubba( 2443838 )

  Wonder if MS dropping Visual Basic has anything to do with its biggest fan, Bill Gates, Leaving the Microsoft Board? Don't get me wrong, it might be time to move on, with the changes in technology, the user interface and all that. It's just that Bill Gates was a VB juggernaut, famous for taunting bottlenecked developers with the assertion that he could dofix whatever the problem was with VB. And if anybody could make sure VB was up to the challenge, it was him.
  • by tepples( 727027 )

    Or perhaps Microsoft was tired of being referred to as 'M$', a name that recalls Microsoft's origin as a publisher of BASIC interpreters. (In the line-numbered era of BASIC, string variable names had to end with a dollar sign.)

    • by Humbubba( 2443838 )
• by Heir Of The Mess( 939658 )

  I think this wins the award for the most stupid thing I've seen on slashdot this year.

  Microsoft the company was founded on porting BASIC to different computers since 1975. They've been improving BASIC for 45 years! and going forward they are still supporting BASIC, they are just not improving it.

  So the next logical question is why are they no longer improving BASIC? Well it's because in 2001 Microsoft invented something better called C#. So going forward C# is future, and C# wil

• by Tony Isaac( 1301187 )

  Yes, I've worked with a couple of guys like you. They do the same job for 20 years and never want to move beyond their favorite technology, like Classic ASP or WinForms.

  Software development is not a trade that can be learned just once. We have to constantly be re-training ourselves, or be relegated to maintaining dying code bases that nobody else wants to touch.

  • by coastwalker( 307620 )

    Also changing languages every 5 years makes it inevitable that we can profit from outsourcing to cheap newly qualified graduates in India. Who needs American programmers over the age of 30 anyway?

    • by Tony Isaac( 1301187 )

      Oh, so you think those cheap, newly qualified graduates in India are actually good at this new technology? You clearly haven't worked with many of them.

      Changing technology is a fact of life, software or otherwise. Cars, medicine, construction, retail, even evolution itself. Evolve, or die, there are no other options.

      • 1 reply beneath your current threshold.
• by aberglas( 991072 )

  The latter sometimes called 'Visual Fred' to make that clear.

  VB.Net should just have been different syntax for C#. Done with the same compiler. So almost exactly the same, mixable in assemblies. Not something thought of as substantially different. Heck, you could even combine the syntax so that people could chose between End Ifs or the ugly {}s line by line. VB.Net is certainly not the same as traditional VB.

  I actually do a lot of work in VBA for Excel. Microsoft cannot kill that because it is actua

  • by mikeebbbd( 3690969 )

    So if VB itself dies off (the story makes it look like it'll take a long time), what about VBA? It has hasn't seem much development in recent years. Open/Libreoffice have a Basic for scripting, too, though not really equivalent to VBA (conversion can't be done on the fly, at least very well, if at all). But the true successor for both (as noted by Z00L00K below) is Python.

• Re: This has happened before, and will happen agai (Score:3)

  The true successor is Python if you like to code in that style.

• 2 replies beneath your current threshold.

Plots End Visual Basic Definition

The End statement stops code execution abruptly, and does not invoke the Dispose or Finalize method, or any other Visual Basic code. Object references held by other programs are invalidated. If an End statement is encountered within a Try or Catch block, control does not pass to the corresponding Finally block. May 13, 2017 GDI+ is an unusual part of.NET. It was here before.NET (GDI+ was released with Windows XP) and it doesn't share the same update cycles as the.NET Framework.