Visual Basic .Net dead? No, it's fifth most popular programming language
zdnet.com
zdnet.com
Now that VB .NET is moving towards being fully supported (it's own namespaces like My, especially) in cross-platform contexts in .NET Core 3.0, there's really no downside to using it.
1) Having the type-name come after the variable name makes for more readable code (in my opinion). The variable itself is more important than its type. (Other languages use a colon. Example: "counter: int;")
2) Having the block "ender" name match the starting name makes for less confusion and block-related IDE miss-matches. All the C# "}" look the same to the IDE and human eye. However, I do wish VB's block naming were more consistent, such as "while...end while" instead of "while...wend". (The later versions mostly fixed this.) In other words, always have the pattern be "X...end X" so you don't have to think.
3) Better switch/case syntax, because it's set-oriented. Needing "break" is silly.
4) Not needing parentheses in IF statements.
On 2, most of the syntax is indentation sensitive, but for types you can optionally annotate them with `class`/`struct`/`interface` and the keyword `end` to finalize them.
Pattern matching in F# is more powerful than simple switch/case statements.
5) Less need to type a semicolon. Although, this increases the need to use continuation marks. The balance may depend on your coding style.
6) Less need to use the Shift key, overall. If you have RSI medical issues, you may like this.