God, I hate VB. All I want for Christmas is for you to smite the retards responsible for its existence
-
...btw, if you're a VB programmer and you think that I was insulting you or anything, then you misunderstood my intentions. ...My gripe is with the language and the reasoning behind the language....VB was designed to give "Non"programmers the ability to write quick, dirty desktop apps. I have a HUGE problem with VB being the language of choice in an enterprise setting, because most of the people that actually would say "Oh, I think we'll write this in VB. It does what we need to do" probably doesn't have the skill to make that decision. VB should never be used for anything other than "my app: I'm building it; I'm supporting it; It's running on my machine" Anything that is to actually be deployed to production should be written in a much more appropriate language because the GENERAL developer base for VB is absolute crap(a bunch of kiddie scripters that read a book and presto: qualified) ...and you end up with systems designed like the one that my snippets illustrate. Again, not insulting ALL VB programmers(A qualified programmer is a qualified programmer is a qualified programmer) ...I write VB(mostly against my will, but what are you gonna do when the system was written in this horrible language and an enhancement comes your way?) ....Gripe about it.....every chance you get. GOD I HATE VB!!!!!
"I need build Skynet. Plz send code"
I suppose you don't actually *believe* in God.
ROFLOLMFAO
-
God, I hate VB. All I want for Christmas is for you to smite the retards responsible for its existence....and if it pleases you, oh God: can you send some of the "Non"s with them? This was written in 2005 in a VB.NET project
GoTo Error_Trap
End TryMe.LBL\_status.Text = "" Else Me.DV\_Search.Visible = True Me.DV\_Results.Attributes("style") = "display:none" Me.LBL\_status.Text = "No Rows Returned." End If Exit SubError_Trap:
ShowError()...The "Business Logic", "Data Access" and "Presentation" layers are maintained not as separate projects inside a solution, but as FOLDERS!!! inside a single project. ...which results in a "hard-wired disgusting switch-boxed bastardization" of the layered pattern ...The mechanism that was chosen by our unqualified senior architect (who makes God knows how much a year) for accessing the database is to have the presentation layer do something like this:
Dim tbl As DataTable
tbl = Common.GetDataTable(SQLScripts.GetBaseEmpSql(UserID))rather than having stored procedures encapsulate the sql scripts, the choice was made to maintain them in code. (Granted, I obfuscated the schema name and each of the table names so that I could post)
Public Shared Function getSQL(ByVal aryPVIDs() As String) As String
'aryPVIDs must be an array of pvids
Dim sql, strSelect, strFrom, strWhere As String
Dim strPVIDs As StringstrPVIDs = Join(aryPVIDs, "','") strSelect = "Select p.ID, p.Ps\_Project\_NBr, " & vbCrLf & \_ " p.Project\_Desc\_txt, pt.Project\_type\_txt, p.project\_type\_cd, " & \_ " p.spread\_method\_cd, sm.spread\_method\_txt, p.project\_mgr\_id, pm.last\_nm||', '||pm.first\_nm ProjectMgrFullName, " & vbCrLf & \_ " p.asset\_mgr\_id, am.last\_nm||', '||am.first\_nm AssetMgrFullName, " & vbCrLf & \_ " p.lead\_eng\_id, le.last\_nm||', '||le.first\_nm LeadEngineerFullName, " & vbCrLf & \_ " p.start\_dt, p.revised\_start\_dt, " & vbCrLf & \_ " p.orig\_serv\_dt, p.revised\_serv\_dt, p.projected\_serv\_dt, " & vbCrLf & \_ " p.host\_flg, p.engineer\_group\_cd, eg.engineer\_group\_txt, " & vbCrLf & \_ " p.Trans\_region\_cd, tr.transmission\_region\_txt, p.comments\_txt, " & vbCrLf & \_ " p.Distr\_region\_cd, dr.distr\_region\_txt, " & vbCrLf & \_ " p.project\_status\_cd, priority\_cd , archive\_flg, " & vbCrLf & \_ " ps.cpp, p.glbu, ps.ci\_status\_nbrI find it ironic that you are blasting VB, but in your messages on your profile you are using access. But in your defense that is some terrible code, where do you work and are they passing out salaries in the 200K range? I think I could move...
-
...btw, if you're a VB programmer and you think that I was insulting you or anything, then you misunderstood my intentions. ...My gripe is with the language and the reasoning behind the language....VB was designed to give "Non"programmers the ability to write quick, dirty desktop apps. I have a HUGE problem with VB being the language of choice in an enterprise setting, because most of the people that actually would say "Oh, I think we'll write this in VB. It does what we need to do" probably doesn't have the skill to make that decision. VB should never be used for anything other than "my app: I'm building it; I'm supporting it; It's running on my machine" Anything that is to actually be deployed to production should be written in a much more appropriate language because the GENERAL developer base for VB is absolute crap(a bunch of kiddie scripters that read a book and presto: qualified) ...and you end up with systems designed like the one that my snippets illustrate. Again, not insulting ALL VB programmers(A qualified programmer is a qualified programmer is a qualified programmer) ...I write VB(mostly against my will, but what are you gonna do when the system was written in this horrible language and an enhancement comes your way?) ....Gripe about it.....every chance you get. GOD I HATE VB!!!!!
"I need build Skynet. Plz send code"
-
God, I hate VB. All I want for Christmas is for you to smite the retards responsible for its existence....and if it pleases you, oh God: can you send some of the "Non"s with them? This was written in 2005 in a VB.NET project
GoTo Error_Trap
End TryMe.LBL\_status.Text = "" Else Me.DV\_Search.Visible = True Me.DV\_Results.Attributes("style") = "display:none" Me.LBL\_status.Text = "No Rows Returned." End If Exit SubError_Trap:
ShowError()...The "Business Logic", "Data Access" and "Presentation" layers are maintained not as separate projects inside a solution, but as FOLDERS!!! inside a single project. ...which results in a "hard-wired disgusting switch-boxed bastardization" of the layered pattern ...The mechanism that was chosen by our unqualified senior architect (who makes God knows how much a year) for accessing the database is to have the presentation layer do something like this:
Dim tbl As DataTable
tbl = Common.GetDataTable(SQLScripts.GetBaseEmpSql(UserID))rather than having stored procedures encapsulate the sql scripts, the choice was made to maintain them in code. (Granted, I obfuscated the schema name and each of the table names so that I could post)
Public Shared Function getSQL(ByVal aryPVIDs() As String) As String
'aryPVIDs must be an array of pvids
Dim sql, strSelect, strFrom, strWhere As String
Dim strPVIDs As StringstrPVIDs = Join(aryPVIDs, "','") strSelect = "Select p.ID, p.Ps\_Project\_NBr, " & vbCrLf & \_ " p.Project\_Desc\_txt, pt.Project\_type\_txt, p.project\_type\_cd, " & \_ " p.spread\_method\_cd, sm.spread\_method\_txt, p.project\_mgr\_id, pm.last\_nm||', '||pm.first\_nm ProjectMgrFullName, " & vbCrLf & \_ " p.asset\_mgr\_id, am.last\_nm||', '||am.first\_nm AssetMgrFullName, " & vbCrLf & \_ " p.lead\_eng\_id, le.last\_nm||', '||le.first\_nm LeadEngineerFullName, " & vbCrLf & \_ " p.start\_dt, p.revised\_start\_dt, " & vbCrLf & \_ " p.orig\_serv\_dt, p.revised\_serv\_dt, p.projected\_serv\_dt, " & vbCrLf & \_ " p.host\_flg, p.engineer\_group\_cd, eg.engineer\_group\_txt, " & vbCrLf & \_ " p.Trans\_region\_cd, tr.transmission\_region\_txt, p.comments\_txt, " & vbCrLf & \_ " p.Distr\_region\_cd, dr.distr\_region\_txt, " & vbCrLf & \_ " p.project\_status\_cd, priority\_cd , archive\_flg, " & vbCrLf & \_ " ps.cpp, p.glbu, ps.ci\_status\_nbrCome to think of it; what is VB implemented in? VB? Any compiler worth its salt is written in the language that it compiles... (C# is the notable exception?) Imagine if VB were open source and being maintained by VB programmers! :omg:
-
Ray Cassick wrote:
The language is syntacticly FINE.
Verbose though.
Ray Cassick wrote:
It is the idiots that USE it that you have problems with.
That's certainly true, but that's the demographic to which it's marketed. And having members of that demographic using C# isn't all that much better either.
-
-
The UnEducated (Mostly Indian/Russian/Chinese) Developers will always write poor programs no matter what the language. VB just makes it eaiser for them to do it! I have seen some excellent and well written VB Programs
Hey! I write good programs! :mad:
ROFLOLMFAO
-
Come to think of it; what is VB implemented in? VB? Any compiler worth its salt is written in the language that it compiles... (C# is the notable exception?) Imagine if VB were open source and being maintained by VB programmers! :omg:
Does this remind anyone of the chicken or the egg problem? :laugh:
ROFLOLMFAO
-
Ray Cassick wrote:
The language is syntacticly FINE. It is the idiots that USE it that you have problems with.
...please tell me that you're just saying that to be argumentative and that you don't actually believe that crap...VB syntax is absolutely disgusting
Ray Cassick wrote:
I have seen equally as dumb ass stuff written in C++, C#, Pascal, etc...
...Don't even get me started on C++ lol ...I *almost* hate C++ more than I hate VB. ...C++ is the bastard child that hangs out in the middle of nowhere that hybridizes the procedural mentality with object oriented design capabilities...when an unqualified programmer gets hold of ANY language, the results are laughable....when a *semi*qualified programmer gets hold of C++, O.....M......G. When you get someone that has a decent grasp of object oriented design, but they use a language that has a direct interface into memory as a staple of its core, you usually end up in the situation where an app starts out rock-solid up front: (Solid implementation of design patterns, the application is programmed to target interfaces; not implementations...etc) but when said "semi-qualified" programmer runs into a tough spot in their design...the approach is usually "Uh-oh...I don't know how to do that....what ****CAN**** I do. And C++ will allow them to take an otherwise well-structured body of work and stitch it together into a frankenstein monster that is more hideous than having to debug FORTRAN's GOTO structure
"I need build Skynet. Plz send code"
-
I find it ironic that you are blasting VB, but in your messages on your profile you are using access. But in your defense that is some terrible code, where do you work and are they passing out salaries in the 200K range? I think I could move...
mr_lasseter wrote:
I find it ironic that you are blasting VB, but in your messages on your profile you are using access.
...upon reading this, I decided that I wouldn't justify that with an answer. But after thinking about it, I decided that I would justify answering it just long enough to tell you that I won't justify that with an answer.
"I need build Skynet. Plz send code"
-
The UnEducated (Mostly Indian/Russian/Chinese) Developers will always write poor programs no matter what the language. VB just makes it eaiser for them to do it! I have seen some excellent and well written VB Programs
I've worked with some damn fine Indian developers ... although come to think about it they all learned the ropes with C++, Java and or C#. Perhaps it is VB :-D
I'm largely language agnostic
After a while they all bug me :doh:
-
Ray Cassick wrote:
The language is syntacticly FINE. It is the idiots that USE it that you have problems with.
...please tell me that you're just saying that to be argumentative and that you don't actually believe that crap...VB syntax is absolutely disgusting
Ray Cassick wrote:
I have seen equally as dumb ass stuff written in C++, C#, Pascal, etc...
...Don't even get me started on C++ lol ...I *almost* hate C++ more than I hate VB. ...C++ is the bastard child that hangs out in the middle of nowhere that hybridizes the procedural mentality with object oriented design capabilities...when an unqualified programmer gets hold of ANY language, the results are laughable....when a *semi*qualified programmer gets hold of C++, O.....M......G. When you get someone that has a decent grasp of object oriented design, but they use a language that has a direct interface into memory as a staple of its core, you usually end up in the situation where an app starts out rock-solid up front: (Solid implementation of design patterns, the application is programmed to target interfaces; not implementations...etc) but when said "semi-qualified" programmer runs into a tough spot in their design...the approach is usually "Uh-oh...I don't know how to do that....what ****CAN**** I do. And C++ will allow them to take an otherwise well-structured body of work and stitch it together into a frankenstein monster that is more hideous than having to debug FORTRAN's GOTO structure
"I need build Skynet. Plz send code"
Alaric_ wrote:
...please tell me that you're just saying that to be argumentative and that you don't actually believe that crap...VB syntax is absolutely disgusting
Seconded. Verbosity for the sake of verbosity. An entire ethos developed around the idea that every concept needs at least 3 words summing 30 characters in length. Painful to write, painful to read. Its like hungarian notation: a useful idea from the '70s painfully continued ad nauseum today.
I'm largely language agnostic
After a while they all bug me :doh:
-
Come to think of it; what is VB implemented in? VB? Any compiler worth its salt is written in the language that it compiles... (C# is the notable exception?) Imagine if VB were open source and being maintained by VB programmers! :omg:
PIEBALDconsult wrote:
Come to think of it; what is VB implemented in? VB? Any compiler worth its salt is written in the language that it compiles... (C# is the notable exception?)
I remember that argument coming up in college between the C/Unix and the VB/Win crowds. The answer turned out to be that VB 4/5 was an advanced OS script while real programmers wrote ANSI C in VI :-D
I'm largely language agnostic
After a while they all bug me :doh:
-
The UnEducated (Mostly Indian/Russian/Chinese) Developers will always write poor programs no matter what the language. VB just makes it eaiser for them to do it! I have seen some excellent and well written VB Programs
sulu wrote:
I have seen some excellent and well written VB Programs
Refuting this is not my point. If you take a skilled developer and tell them to write something in VB, they can apply their skills to a bad situation and usually pull an app out of the crapper. My point is that VB was never a language that was targeted at SKILLED developers. VB is a language that is targeted at...say, an accountant that knows how to write Excel macros and wants to come up with something to impress their manager. ...That's all fine and cool; IF IT STAYS THERE!!! ...when those people teach themselves VB and then consider themselves a "programmer" and slide into IT to screw systems up that someone like me has to go in and fix, there is DEFINITELY a problem. Like I said: "A skilled developer is a skilled developer is a skilled developer" ....taken further, "A skilled C++ developer is a skilled Java developer is a skilled VB developer" ...The language itself is irrelevant. You should be able to throw any language at a skilled developer and have them write proficiently....the architects at Microsoft tried their damnedest to break this fact when they formulated Visual Basic
sulu wrote:
The UnEducated (Mostly Indian/Russian/Chinese) Developers will always write poor programs no matter what the language. VB just makes it eaiser for them to do it!
I nearly completely disagree with this stereotype. There is an undeniable presence of "brain dump certifications" that are handed out overseas, but I don't think that you can make the blanket statement that Indian, Russian, or Chinese developers are intrinsically less qualified, which I'm not sure you actually are saying...maybe you're just using heavy-handed statements
"I need build Skynet. Plz send code"
-
Ray Cassick wrote:
Why is your post not titled "I hate dumb ass VB programmers"?
Because if you think that's what I was saying, you either are incapable of(or you simply posted before)reading my follow-up to my original post. I'll quote myself on this one:
Alaric_ wrote:
...btw, if you're a VB programmer and you think that I was insulting you or anything, then you misunderstood my intentions. ...My gripe is with the language and the reasoning behind the language....VB was designed to give "Non"programmers the ability to write quick, dirty desktop apps. I have a HUGE problem with VB being the language of choice in an enterprise setting, because most of the people that actually would say "Oh, I think we'll write this in VB. It does what we need to do" probably doesn't have the skill to make that decision. VB should never be used for anything other than "my app: I'm building it; I'm supporting it; It's running on my machine" Anything that is to actually be deployed to production should be written in a much more appropriate language because the GENERAL developer base for VB is absolute crap(a bunch of kiddie scripters that read a book and presto: qualified) ...and you end up with systems designed like the one that my snippets illustrate. Again, not insulting ALL VB programmers(A qualified programmer is a qualified programmer is a qualified programmer) ...I write VB(mostly against my will, but what are you gonna do when the system was written in this horrible language and an enhancement comes your way?) ....Gripe about it.....every chance you get. GOD I HATE VB!!!!!
"I need build Skynet. Plz send code"
-
God, I hate VB. All I want for Christmas is for you to smite the retards responsible for its existence....and if it pleases you, oh God: can you send some of the "Non"s with them? This was written in 2005 in a VB.NET project
GoTo Error_Trap
End TryMe.LBL\_status.Text = "" Else Me.DV\_Search.Visible = True Me.DV\_Results.Attributes("style") = "display:none" Me.LBL\_status.Text = "No Rows Returned." End If Exit SubError_Trap:
ShowError()...The "Business Logic", "Data Access" and "Presentation" layers are maintained not as separate projects inside a solution, but as FOLDERS!!! inside a single project. ...which results in a "hard-wired disgusting switch-boxed bastardization" of the layered pattern ...The mechanism that was chosen by our unqualified senior architect (who makes God knows how much a year) for accessing the database is to have the presentation layer do something like this:
Dim tbl As DataTable
tbl = Common.GetDataTable(SQLScripts.GetBaseEmpSql(UserID))rather than having stored procedures encapsulate the sql scripts, the choice was made to maintain them in code. (Granted, I obfuscated the schema name and each of the table names so that I could post)
Public Shared Function getSQL(ByVal aryPVIDs() As String) As String
'aryPVIDs must be an array of pvids
Dim sql, strSelect, strFrom, strWhere As String
Dim strPVIDs As StringstrPVIDs = Join(aryPVIDs, "','") strSelect = "Select p.ID, p.Ps\_Project\_NBr, " & vbCrLf & \_ " p.Project\_Desc\_txt, pt.Project\_type\_txt, p.project\_type\_cd, " & \_ " p.spread\_method\_cd, sm.spread\_method\_txt, p.project\_mgr\_id, pm.last\_nm||', '||pm.first\_nm ProjectMgrFullName, " & vbCrLf & \_ " p.asset\_mgr\_id, am.last\_nm||', '||am.first\_nm AssetMgrFullName, " & vbCrLf & \_ " p.lead\_eng\_id, le.last\_nm||', '||le.first\_nm LeadEngineerFullName, " & vbCrLf & \_ " p.start\_dt, p.revised\_start\_dt, " & vbCrLf & \_ " p.orig\_serv\_dt, p.revised\_serv\_dt, p.projected\_serv\_dt, " & vbCrLf & \_ " p.host\_flg, p.engineer\_group\_cd, eg.engineer\_group\_txt, " & vbCrLf & \_ " p.Trans\_region\_cd, tr.transmission\_region\_txt, p.comments\_txt, " & vbCrLf & \_ " p.Distr\_region\_cd, dr.distr\_region\_txt, " & vbCrLf & \_ " p.project\_status\_cd, priority\_cd , archive\_flg, " & vbCrLf & \_ " ps.cpp, p.glbu, ps.ci\_status\_nbrSadly, it's not the retards writing the VB net compiler that want backwards compatibility. It's the retards using the old VB syntax that want it. I for one, can't stand the old VB6 crap and the "shortcuts" and implicit conversions it does in the background. If it was up to me, "On Error Goto", and alot of other pre-VB.NET crap, would have been tied to a post, blindfolded, and asked what it wanted on its Tombstone.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007 -
Sadly, it's not the retards writing the VB net compiler that want backwards compatibility. It's the retards using the old VB syntax that want it. I for one, can't stand the old VB6 crap and the "shortcuts" and implicit conversions it does in the background. If it was up to me, "On Error Goto", and alot of other pre-VB.NET crap, would have been tied to a post, blindfolded, and asked what it wanted on its Tombstone.
A guide to posting questions on CodeProject[^]
Dave Kreskowiak Microsoft MVP Visual Developer - Visual Basic
2006, 2007Dave Kreskowiak wrote:
I for one, can't stand the old VB6 crap and the "shortcuts" and implicit conversions it does in the background. If it was up to me, "On Error Goto", and alot of other pre-VB.NET crap
"On Error Goto" was never a correct implementation of exception handling. I say that I hate "VB" because Visual Basic is the most popular incarnation of the BASIC language (in the current .NET flavor), but more accurately, I should have said that I despise BASIC ...does anyone that writes BASIC even know what it is??? It stands for Beginner's All-purpose Symbolic Instruction Code. If you're a Beginner, writing BASIC is completely understandable. But you MUST realize that it is intended for use by non-programmers as a stepping stone to whatever language you go to after you are comfortable enough to step up
"I need build Skynet. Plz send code"
-
Hey! I write good programs! :mad:
ROFLOLMFAO
Ri Qen-Sin wrote:
I write good programs!
I believe you... because you didn't say, "I write programs good!" :-D
-
Does this remind anyone of the chicken or the egg problem? :laugh:
ROFLOLMFAO
Ri Qen-Sin wrote:
Does this remind anyone of the chicken or the egg problem?
Nope. There is bootstrapping[^]
-
God, I hate VB. All I want for Christmas is for you to smite the retards responsible for its existence....and if it pleases you, oh God: can you send some of the "Non"s with them? This was written in 2005 in a VB.NET project
GoTo Error_Trap
End TryMe.LBL\_status.Text = "" Else Me.DV\_Search.Visible = True Me.DV\_Results.Attributes("style") = "display:none" Me.LBL\_status.Text = "No Rows Returned." End If Exit SubError_Trap:
ShowError()...The "Business Logic", "Data Access" and "Presentation" layers are maintained not as separate projects inside a solution, but as FOLDERS!!! inside a single project. ...which results in a "hard-wired disgusting switch-boxed bastardization" of the layered pattern ...The mechanism that was chosen by our unqualified senior architect (who makes God knows how much a year) for accessing the database is to have the presentation layer do something like this:
Dim tbl As DataTable
tbl = Common.GetDataTable(SQLScripts.GetBaseEmpSql(UserID))rather than having stored procedures encapsulate the sql scripts, the choice was made to maintain them in code. (Granted, I obfuscated the schema name and each of the table names so that I could post)
Public Shared Function getSQL(ByVal aryPVIDs() As String) As String
'aryPVIDs must be an array of pvids
Dim sql, strSelect, strFrom, strWhere As String
Dim strPVIDs As StringstrPVIDs = Join(aryPVIDs, "','") strSelect = "Select p.ID, p.Ps\_Project\_NBr, " & vbCrLf & \_ " p.Project\_Desc\_txt, pt.Project\_type\_txt, p.project\_type\_cd, " & \_ " p.spread\_method\_cd, sm.spread\_method\_txt, p.project\_mgr\_id, pm.last\_nm||', '||pm.first\_nm ProjectMgrFullName, " & vbCrLf & \_ " p.asset\_mgr\_id, am.last\_nm||', '||am.first\_nm AssetMgrFullName, " & vbCrLf & \_ " p.lead\_eng\_id, le.last\_nm||', '||le.first\_nm LeadEngineerFullName, " & vbCrLf & \_ " p.start\_dt, p.revised\_start\_dt, " & vbCrLf & \_ " p.orig\_serv\_dt, p.revised\_serv\_dt, p.projected\_serv\_dt, " & vbCrLf & \_ " p.host\_flg, p.engineer\_group\_cd, eg.engineer\_group\_txt, " & vbCrLf & \_ " p.Trans\_region\_cd, tr.transmission\_region\_txt, p.comments\_txt, " & vbCrLf & \_ " p.Distr\_region\_cd, dr.distr\_region\_txt, " & vbCrLf & \_ " p.project\_status\_cd, priority\_cd , archive\_flg, " & vbCrLf & \_ " ps.cpp, p.glbu, ps.ci\_status\_nbrThat is just plain hideous.
"Real programmers just throw a bunch of 1s and 0s at the computer to see what sticks" - Pete O'Hanlon