Let's discuss where VB is going and interact with some of those that are making it happen!
the biggest reason to use WPF is because of a "feeling" that I "should" use newer technologies because they're newer.
I disagree. I create new Winforms only for fast samples and demos, but in any real project I use WPF, as it makes designing the UI easier especially in DB apps, as I can show the data in anyway I imagine, and make complex views by just using lists and expanders. Easier
doesn't ignore that xaml needs some effort to master, but once a data form is well designed, all other forms will be done fast and easy. Also, wpf needs a lot of workaround and tricks to overcome many issues, but it is a very flexible framework, and and we have control over every component of it, so, workarounds are always available.
I like to get inspired by looking at the construction of WinForms screens on this channel, it's in Spanish, use automatic subtitles.
https://www.youtube.com/watch?v=MiA7vKqtF5Q&list=PLqjdFmR_HdQQWykGStUMREdQbUnRIZ1X2
https://www.youtube.com/watch?v=n6Ea5xCNMZc&list=PLqjdFmR_HdQT-XPcjkyyRkEYZLwL6oUwa&index=1
It would be more productive if your just update things that are broken
This is not possible, because if i want to do so, I would need to understand the whole app first, and I will modify things while I am walking through the code, so, I can work on the app years to come!
This is exactly one of my favorite areas in programming, but currently ModVB is my priority after i get free from sVB (If this is possible :( ).
Checking in (Wave 2)
@AnthonyDGreen
Congratulations Grandmaster Anthony D. Green, I really like the scope of technologies you are focusing on, keeping VB.NET competitive and with more mature technologies without an excessive number of tools is very important.
In this new journey of VB, which begins with your leadership, not having confusion and countless tools to do the same thing is very important, being simple and direct has enormous advantages.
VB for desktop is already wonderful.
VB for Web needs improvement, but being in ASP.NET and being competitive in various scenarios is what matters.
VB for mobile needs to be born, but we don’t need to have 50 different options to do the same thing, we just need a simple, objective and well-documented tool.
VB for MS office needs to be more of an option to VBA and not just point to Python as a possible replacement.
VB in the browser may be interesting in the future, as it is a trend of C# and Python.
With all these precautions not to create too many tools that confuse rather than simplify the user, we can be another simple, productive, economical and very viable language option for new projects.
We can’t make the same mistake as C# which is getting too big, unfocused, ineligible for many developers when the team is large, in addition to having totally confusing documentation due to too many tools. We don’t need to follow this path or even follow the path of C#, C# aims to commercially please new developers, and as new languages appear like Python, C# tries to approach, this in the future may be a success, but it may be make a big mess.
We need to be practical, readable, fast and well documented, we need to go back to having the simple, easy and RAD language classification and be competitive with Python and if possible even with Golang, which today is an option for C#.
The Community should soon help with the integration of the main C++, Python, C# and JavaScript libraries making them consumable by VB.
<RunAtClient>
, so the compiler compiles it to wasm or JS. So, we can call such function from Razor pages. I see this easier that Blazor components, and if implemented in VB, it will e combined with XML literals very easily to create the razor views like I do in Vazor.