-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not for beginners. Not for professionals: VB.NET is in indeterminate state! #452
Comments
Like in pre VB6 we should create multipage Wizard based template(s) to create a UWP VB project to incorporate AAD login, complex navigation, theme (with customization), Integration of Facebook, Twitter etc. authentications, Email/SMS integration, MQ/Kafka integration, EF Core scaffolding, etc. At the end of the 5-10 page wizard, the template should create a comprehensive full blown UWP app in VB.NET and leave the developer to concentrate only on implementing business logic. This itself will be a USP for VB.NET. @VBAndCs, for your nephew I would suggest a good starting point for VB which is "smallbasic" from Microsoft. |
Relevant: #446 Perhaps take a clone of @AnthonyDGreen 's fork? |
@rrvenki |
This issue doesn't seem to be actionable. Closing out. |
My nephew is 13 years old. I am trying to teach him VB.NET. There are tons of basic facts that he should learn before producing any thing useful. The worst is that he and his generation are not interested in desktops, as they live in mobile and tablet worlds!
He keep asking me about who would use such example in real world, and he is absolutely right!
I keep telling him: these are the basics but you can build mobile apps later!
Of course I am a liar, because he can't do this with VB.NET!
VB6 was easy to start with, even with no programming basics.
I know that learning programming is a different thing than learning programming language, but these young impatient kids need to do some attractive apps first before sinking in programming science.
The shocking fact is that VB.NET in its current state is not a beginner language any more, nor a professional one! It is a thing that needs years of learning just to be abandoned to C# at last!
I think VB.NET needs to be redesigned from scratch, to achieve two goals:
This can be done by adding more wizards and generated code (preferred to be semi hidden unless the programmer navigates to). May be there should be some basic code blocks and a designer to map them on, so VB gains its missing Visual part! Make use of light switch in some way.
Winforms also can have more composite controls to be used with the most used data entry forms and alike.
In a few words: beginners should start production in seconds.
If VB.NET is domed to be a desktop language, this is a death sentence.
So, VB.NET must target ASP.NET Core and Xamarin.
By the way, my nephew got confued with Char type and VB6 Chr function, so I had to use Convert.ToChar to be consistent. There are a lot of confusing naming conventions between VB and the framework. All that legacy non sense is a heavy burden over beginners. I strongly advice to look ahead and break the backward computability.
Its time to create a new clean VB.Core lang for new generation.
I repeated that many times before, trying to suggest alternative syntax for some blocks to be more familiar to beginners as I imagined. Now I am talking based on a practical experience.
The text was updated successfully, but these errors were encountered: