10
j0zeft
8d

Started a job as a full stack developer. My first task was shocking! Do these small edits on this backend script that collects stuff from one database and edits the entries in another... piece of cake so far!

Here is the project on the TFS...
HOLD ON! IS THIS VISUAL BASIC?!!
I came here to do .Net framework development and .Net Standard... I wasn’t told that there will be VB, I have never used vb.net before.

Now... that I’m going to maintain this script in the future, I decided to rewrite it in C#, few things I learned on my journey of doing this:
1- There is an access modifier in VB called Friend
2- There is a data structure/type called Collection, it’s a value,key pair! Not key value pair... Value first, then key!!
3- Do you know how null is null everywhere?!! In VB they call it Nothing! Yes, as in...
if(myVar == nothing)
{
//stuff
}
Asking the guy responsible for that choice... he thinks VB is easier to read than C#
I DONT WANT YOU TO READ IT, I WANT IT TO MAKE SENSE AND WORK WITH THE REST OF THE C# CODE WE HAVE!!

Comments
  • 3
    Even worse, "Nothing" is not only "Null", but the empty / default value for types that are not nullable.
  • 0
    This is one weird language!
  • 2
    1) isnt that the same as protected? I think c++ has it too

    3) lot of languages use None, its not that weird
  • 3
    I started out with VB.Net and was scared when I looked at C# because it had all the { and }s and semicolons and way less words I knew etc
    Glad I made it 😂
  • 3
    @Kimmax Same journey as me. I'll never go back to vb.net
  • 2
    @ultimaterage absolutely not haha
    I can't even write it anymore
  • 0
    I’ve come to prefer how rust handles null, with the Option type and Some(val)/None
  • 0
    @Plasticnova most modern languages do that
  • 0
    Mmm, Variant.

    Also, vb.net isn't VB. Just saying.
Add Comment