vblang
vblang copied to clipboard
dotnet
Voice your opinion on VB support on MAUI (next evolution of Xamarin.Forms)
https://github.com/dotnet/maui/issues/115#issuecomment-634447806
vb.net is basically dead. I doubt it will even be supported in .net 7
Show them otherwise...
No doubt vb needs to be here. It's the 5th or 6th most used dev lang in the world, for both front ends and back ends, for CLI and GUI.
I now think that Microsoft's implementation of Visual Basic on .Net (either framework or core) is dead.
@AdamSpeight2008 I agree. Even WinUI 3 (a new Windows 10 desktop development workload, vNext of UWP) is dropping VB support. https://github.com/microsoft/microsoft-ui-xaml/issues/2497#issuecomment-632368899
I will then keep using VB.net on Winforms , maybe migrating to .net core 5. It's not for MS to push me what tools and workloads.
@Happypig375 I don't think one issue can capture the needs of both languages here. Can you file a separate issue related to VB support if that is important to you?
@sharwell Being mentioned in the most liked issue is definitely better than opening an entirely new issue. Opening a new issue will result in significantly less visibility.
It cannot be denied that VB is a beginner-friendly language. The most important thing is that for some old VB GUI programs, this is an important support for cross-platform, and it can run cross-platform with few changes. And for some students, they may not need to write programs often afterwards. VB is a convenient language for them, and they still need these. This passage was translated into English by translation software, and there may be some errors.
Is Maui the next version of Xamrin.Forms or WinForms or both or something else?
Is Maui the next version of Xamrin.Forms or WinForms or both or something else?
Xamarin.Forms https://github.com/dotnet/maui
Maybe it is useful if vb project template be added. https://github.com/AvaloniaUI/Avalonia
No other technology that VB doesn't support like Blazor, Vazor or Xamarin will make such a difference, we can safely skip those tools. If there is one tool that every developer, business, and government should strive to support in VB.NET, it is MAUI.
VB is much more intuitive and faster to code creation than C# (and its terrible ";").
C# was a try of Microsoft to bring the people involved with "C" to its new language environment, with minor changes and traumas.
Who says VB "is for dummies", does not know what code is running on the most advanced companies around the world - at least, for the time the language exists and the migration done from VB5 and VB6 to it. We must remember that C# was created in 2000 (and VB6 came in 1998).
VB has been proving as reliable and fast as C# (since the ILASM is the same for both!). Microsoft simply discarding the VB language from any new environment is a big mistake.
Honestly, I'm a little tired of Microsoft, they want to determine what to use by pushing C# on all developers, that's unfortunate!
I don't like C# and period.
Killing VB seems more like an attempt to put C# in a better position in the language rankings, but it won't beat JavaScript, Python and Java, 10 years from now it may not even be those languages anymore.
I hope VB.NET can get out of Microsoft and find its own way. My fingers are crossed for that to happen!
meanwhile, what I can't do in VB I'm doing everything within the JavaScript ecosystem.
C# is not my choice.
@cristianlt23 That's unfortunate too because JavaScript is such a terrible platform in areas where VB and .NET really shine.
@ocdtrekkie
I agree in many ways with what you said.
But you know, Microsoft has been beating me for a long time, since VB5, promises with Windows Phone, promises with VB.NET, we invest money and a lot of time and suddenly, "we are not going to evolve VB.NET anymore".
I know Microsoft is looking for profit and ROI, but there are actions by companies that just can't be taken that way.
For these reasons I'm migrating to another ecosystem, sometimes we get tired of always moving forward and supporting a company that always does this.
Do you think that 5 years from now, if C# doesn't give the expected result, Microsoft will continue to invest? I don't think so and the problem is with the community.
so if I'm going to face a language that's in the hands of a community, I'm going to choose one that already has a lot of experience in the community.
But you know, Microsoft has been beating me for a long time, since VB5, promises with Windows Phone, promises with VB.NET, we invest money and a lot of time and suddenly, "we are not going to evolve VB.NET anymore."
Yes, I agree that MS made a lot of wrong choices. I was the first Brazilian to launch an app into the WindowsPhone Store - money spent on hardware, software, and many hours of study. And, suddenly (and after MS bought Nokia), everything went into the bag... the project was dead.
But I can't see another ecosystem with such performance and flexibility as VB.NET. I hope some people produce "independent compilers" and IDE to support it for a long time.
@DBenS
That's cool, we're Brazilians hahaha.
as you said, I also hope that compilers and an IDE will be created for our beloved VB.
https://download.cnet.com/Visual-Basic-VB-NET-Compiler/3000-20414_4-78387115.html Just saw this VB compiler for iOS. Looks like there are several other VB compilers for other platforms including multiplatform. Not all are free.
At this point, if you want to keep using Visual Basic your best bet is Mercury.
At USD$600/year?
Not ideal obviously, but if you’re making money from your work and you are adamant you’re not going to use any other language, it’s an option none-the-less.
At this point, if you want to keep using Visual Basic your best bet is Mercury.
At USD$600/year?
Not ideal obviously, but if you’re making money from your work and you are adamant you’re not going to use any other language, it’s an option none-the-less.
It's an option - thanks for sharing it.
But, as @cristianlt23 said, considering a complete MS free IDE (for "Community"), Mercury is not an option for standalone programmers.
And, since the MS compiler creates the same code and shares the same libraries for C# and VB.NET, and considering the base of programmers (and companies) developed for so many decades for VB, it would be a wrong option for Microsoft to obligate them to migrate.
This behavior will affect the confidence to Microsoft for long-term languages. Who could ensure that the same migartion wouldn't be performed with C# to any new language in few years ahead?
There was a joke in the 90s when I was using FORTRAN77: "50 years from now there will be a programming language, and it will be called FORTRAN." Same thing for VB.NET, 50 years from now, VB.NET will be used. I am sure the big banks (with a lot more money than MS) just love the idea of deprecating VB.NET.
For those who commented on speed, it doesn't matter, since both C# and VB.NET converge to MSIL.
In the future, MS will be exculpating over their decision to deprecate VB. In fact, I wouldn't want to be in the board room when a president says: "I want all the names of executive leadership who are responsible for killing VB."
When I noticed the word "MAUI," I immediately thought that MS will change the name of MAUI and eventually not support it, only because MS tends to be "all mach and no heading" or "a high-speed cheerleader", which are fighter jet pilot terms that imply: you're fast, but you don't know where you're going.
I invite you to access:
-
https://gitter.im/VB-NET/community
and if you feel convinced, I invite you to visit
- Checking in (Wave 2)
https://anthonydgreen.net/2022/12/28...ave-2/#respond
- https://www.patreon.com/ThatVBGuy
Thanks for reading