this post was submitted on 05 Jul 2023
13 points (76.0% liked)
Programming
17424 readers
27 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
First, of course, use whatever you're comfortable with.
Second, a lot of that advice you see is about long-term development on large projects. Often you don't know if a little side project is going to turn into something huge but it'd be nice to have started it in something that will be more easily maintainable down the line.
May I just ask how VB.NET code isn't maintainable? Not attacking you here, just out of curiosity. My board game server and client together amount to multiple thousand lines of code, as they're very feature rich and at the moment, it's not really hard for me to maintain things. It's not public yet, though. Still active development phase.
TL;DR: Lots of old code written by VB6/VBA programmers in the wild. It's way more holistic than C-hacker-ish C# code.
Speaking from a bunch of legacy projects, you will likely encounter:
I'm currently maintaining a multi million line VB.NET code base, the foundations of which were hastily laid down by young and inexperienced devs realizing a business opportunity in the early 2000s. Lots of these out there in the enterprise world from what I hear and I think this is where there the language gets its reputation from. Sure, at its best it's just C# with words in place of curly braces, but that's only the case with well disciplined programmers (and even then, why not just use C#?). Option Strict is, well, just an option, and even the infamous
On Error Resume Next
is still usable in VB.NET to this day afaik. A lot more room for shooting yourself (or the next person reading your code) in the foot if you don't know what to look out for.I was mostly thinking about PHP with that comment. Which has some serious issues with how modules from other files are included and general structure. It's possible to write well organized PHP projects but it takes discipline, it doesn't happen organically, and its really hard to fix once the project has grown significantly.
I haven't used VB since
VB.NET
2003 so I hesitate to speak on that directly. Professionally I work across multiple OS's and architectures so all .NET languages are kinda no-go's. That's where C++ really shines.That applies to most languages, that you can write an awful unmaintainable mess. Especially when the project started by someone with little experience, or no knowledge about suitable design patterns.
How about Java?
.NET has had support for Linux, Mac and ARM for a while now.