Ah, that's quite a huge difference!

I'm not a C programmer, so forgive my eventual stupid question: there is/was also a language called 'D' which claimed to enhance some of C flaws. I'm not a D programmer either. Anyone here with enough ZIG and D experience to compare both?

:thumbsup:

by the way, this dude revealed a secret feature of goto in c++ that apparently very few people know about (from 31m:15s): CppCon 2019: Miro Knejp “Non-conforming C++: the Secrets the Committee Is Hiding From You” - YouTube[^] disclamer: i myself am a visual basic guy, so goto caught my attention. i further have no clue about c++

totally agree! stuff in text files and [Agent Ransack] to find things back very fast.

yeah, teenagers using psychedelic stuff in the weekend, then hit the commit button monday at work after quickly adjust the ui to match what they have experienced in their trip. you are the problem ;) ! navigate to their site only when having some dmt stuff in your blood as well, and you'll be just fine :)

haha! that's a good one :-)

Deno? [^]

VB pile of crap? Really? Funny how we see things. When I look at all the {{{{{}}}}} and ;;;;;;;;; in other languages, I feel sorry for all that syntax crap they have been born with. A lot of people like that shit though, so it must be some sweet crap.. Functionality wise, VB and C# for example visite the same barbershop to get their new identical look, ready to be swallowed up by the machine. So if you are not talking about syntax, then C# is in this case a pile of crap too. I doubt that.

By the way, no more _ required to break a line in VB.Net anymore..

I endorse Balboos for his suggestion of w3schools. For non interactive learning tools, this is one of the best out there if not the best!

At this speed, by the year 3500, if you hit F5, you can just forget about the whole thing, go live and die, and leave the debugging to your children. Also, I think that Visual Studio processes that people will use must be lauched by their grand-parents when the programmer's parents are still in foetus stage. By the time one can program, 2 generations later, the start pages of all instances will be ready to go. If you accidently close an instance, be careful... but you still have more probably. But if you need to reboot that pc, oops...

There is no cloud! It's just someone else's pc! (Read it somewhere)

Don't forget to mention that it's also quiet slooooww! (Wrong settings? Wrong machine?)

There is no cloud! It's just someone else's machine...

:)

I don't like C# either, I'm more into VB or languages without all the {{{}}} and ;;;;; But since there are a lot of translaters out there to convert VB into C#, we don't have to worry. In my case, I guess I just have to code in VB and once done, let an engine translate it to me into C#. Never tried Xamarin though, so no proof that will work well but it seems doable. It also seems that Xamarin uses the MSIL code, that same code VB is turned into just like C#. If this is true, VB can easily be implemented as well in Xamarin. To be continued...

Lead, follow or get out of the way!

Well said, @cwmillerli! Some kind of Upside Down Aikido Programming... ;-) Here is the thing: Since you don't want to quit, one of you two guys will have to be flexible, at least at the beginning, and that is you. Before the boss will listen to you, you first have to gain his trust. To do that, he needs to feel that you take him seriously and that you listen to his needs. Giving him that first screen will do that, so do it. Tell him just once very strongly but shortly, with whitness or proof to support it later, that his methode will cost more money and time at long term. You can then recall this moment later when things really get out of hands. Make sure you avoid repeating it after having said it. What's the big deal if you have to rebuild to often because of his approach? You don't want to leave, he is not listening but it's his company! You don't have a choice. Do you? Some people only listen when they get hit. So let him feel the consequences of his methode if you're so sure that is what will happen finally. What do you care? It's his company, not yours. And if this really get bad along the way, well, you've told him, right! If you feel you can code in such a way to limit the dammages because of his approach, do that. If it's too much work for you, leave it. One positive thing is that you'll be having a job because there is so much to do/fix. That counts too. It won't be your fault if the project takes too long, so why bother? We, at CodeProject, we all know you've tried :-) Good luck!