One big pain in the arse

  • Thread starter Thread starter Steve Schroeder
  • Start date Start date
S

Steve Schroeder

Man is this whole .Net thing one big pain in the arse!

Debugging has become some black art accessible only to those most in the
know.

Nothing works as expected.

Language changes were only made for the sake of change and do nothing to
make my job 'easier'.

Phew.

Got that off my chest. Back to our regularly scheduled program.
 
Steve - would you care to elaborate on why you believe any of this. I
guess you're talking about VB.NET b/c C# didn't have a previous version.
VB.NET is so vastly superior to vb that it'd be hard to begin to list them
all. The IDE and Debugging in .NEt is also a lot nicer in every way I can
think of - but I'm interested in specifically what you find different. In
no way am I being argumentative, just genuinely interested in why you feel
this way.

Cheers,

Bill
 
I was really just blowing off some steam as I wrangle my head around getting
something done.

I would however make the argument that, since VB.Net is so vastly superior
and different from classic VB it constitutes a new language. Correct? If so,
MS is asking an awful lot of the business world to adopt a 'new' language
for business critical applications.

That said, I'll get over it. Just blowing off some steam.
 
Man is this whole .Net thing one big pain in the arse!
MAN! Visions of my complaints of linux, java, j2ee, WebLogic, JBuilder, and
MySQL. Although the technology stack is different, the attitude,
frustration, determination to pound the crap out of the monitor is shared.
:<
Language changes were only made for the sake of change and do nothing to
make my job 'easier'.
To be honest, it might be as simple as a change of perspective. I found I
wasn't able to "think" like a java/linux person which lead to most of my
frustrations. :< I used to do VB (classic I think it's called now), moved
to java and am now a much happier person now that I've moved back to MS, C#.
Got that off my chest. Back to our regularly scheduled program.
HAHA! Yup, I know how you feel. Just keep plugging away! As you can see
(I hope :>) there are other people around who are willing, and some hoping
to help out. Much better attitude than you would receive on the linux/java
newsgroups! :<

Good luck and keep a bottle of tylenol handy. :>
 
Steve,

You are not the first one who write this. C# and VBNet are used already
again for a long time now.

Most people who wrote messages like yours, wrote after some months messages
like this. "I first thought it was awfull, now they have to pull me back on
my hairs to classic VB and I will scream".

By the way, this is an ADONET (DATA) newsgroup. A newsgroup as

microsoft.public.dotnet.general

is probably a better place for a discussion like this.

Cor
 
I'm well aware of what topic this group is. I already expressed my
frustration and have moved on.
 
Boy isn't that honest truth! Thanks for the encouragement. I'm further along
than my machinations would allude to.

Flip said:
Much better attitude than you would receive on the linux/java newsgroups!
:<
 
Steve, I wasn't being critical and if I came off that way, my apologies.
You have every right to blow off steam and I wasn't giving you a hard time
about it. If I came off that way (it wouldn't be the first time) I
apologise.

To your question specifically about it being a brand new language, I would
answer unquestionably, Yes, it's a brand new language. The whole .NET
Paradigm is such that in order to use it effectively, you should concentrate
on leanring .NET - not any given language. If you switch on Option Strict in
VB.NET (which, with very limited exception is definitely something you
should do) you'll quickly come to realize how different VB and VB.NET are.
C++ and Java Programmers often talked a lot of smack about VB being a Toy
language. No one that knows what they're talking about could say the same
for VB.NET. They could criticize .NET, or Memory Managed languages in
general, but VB.NET is every bit as real a language as anything else.

..NET can definitely be frustrating at first man, no doubt about it. A lot
of that is offset by the improved IDE but the learning curve is significant.
Your statement about Microsoft asking a lot - well,
http://classicvb.org/petition/ - you definitely aren't alone in that regard.
 
No you didn't come off as critical by any means. I just tend to speak
outloud sometimes. I'm an only lonely programmer here at a law firm in Mpls,
so having conversations with other people 'just like me' is important to me.
I appreciate your candor :)

I'll get accustomed to the new language, I'll just kick, scream and bite
along the way :)
 
Doing things .NET - under the managed runtime. There's a marked difference
between how you'd do stuff in C++ for instance and a memory managed
environment.
 
see the 2 holed teeth .. good good !! :). Now get back to work !!
OK OK! Give me a sec. DOH! I just got to find a C#/.NET job now! This
darn java/jsp gig is kill'n me! :<

Oh ya, back to work! :> :>

PS Steve, seems like other ppl went through the same things as you. Not
that it's a good thing, but at least you're not alone, which you already
know now I think. :> When I was learning java/jsp, there was NONE of this
camaraderie what-so-ever. Yup, STILL blowing off steam, that's how
frustrated I was and still am with java. :<<<< oh man, have to get back to
work, getting all aggitated just thinking of it. Oh wait, my job IS java.
:< SHOOT! :< Just can't win today! :>

Anyways, have a good one! :>
 
Honestly, I'm fascinated that Java has permutated the IT business to a
degree that actually justifies a permanent Java programmer position. :)
 
Back
Top