Re: Decompiler.NET reverse engineers your CLS compliant code

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: CJ Taylor (cege)
Date: 09/25/04 

Date: Sat, 25 Sep 2004 14:26:50 -0500

Wow... a trolling we will go I see...

> > Isn't that a matter of perspective? tiny to you... perhaps could have
> > cost
> > a business money... Not too small to them is it?
>
> Our customers test their own software. If they encounter any code
generation
> issues related to using our product, they would contact us and we would
> resolve the issue by releasing an updated version that corrects the issue.
> The small issues that you identified such as your nested array
> initialization example resulted in generated code that would expose the
> issue at compile tiime. Since noone reported it, the issue either didn't
> affect them, or they fixed the generated code manually and didn't tell us.
> Either way, it couldn't have cost them any money and I'm sure none were
> aware of it since our customers enjoy the support that we provide to them
> and would not hesitate to let us know if they detected any code generation
> issues.
>
>
> > Him... must be why everyone on *here* says your product is inferior.
> The people shouting on here are you, Nak, and <a>. None of you are
respected
> by anyone in this group, you only post intentionally malicious messages
> designed to create controversy, and have been reprimanded by several
others
> in this thread besides myself. All of you attempted to remain anonymous,
and
> continue to post intentionally false statements about our company and
> product. You have even commented that you are intentionally looking to
start
> up non-technical arguments just for your own entertainment at the expense
of
> the time that you continie to waste for everyone else still reading this
> thread who is really interested in decompilation technical issues. Since
you
> are not, you and your friends should probably leave since you are not
> interested anyway in our products, and you are wasting the time of the
> entire developer community reading this thread because they are interested
> in the technical content that it contains and have not yet given up trying
> to filter out your spam messages.
>
> > I just hear the same
> > speech over and over about how many bugs you've reported to other
> > companies,
> > and how you have no bugs outstanding?
> You read this thread voluntarily.Since you aren't interested in our
> products, and noone else wants to read your non-technical posts, then why
> don't you just stop reading the thread since it's title indicates that it
is
> related to our product which you are not interested in. Your false
negative
> statements about it serve no purpose except to waste everyone's time
> including your own. You and your friends should stop attacking our
company
> and others in public newsgroups if you goal is to not give those companies
> additional exposure, but we must respond to defend our products each time
> one of you posts inaccurate and misleading information that interferes
with
> the success of serious developers who are genuinely intersted in the
> technical topics that our product addresses.
>
> > There are probably MANY
> > bugs in your software that your not aware of. That's software. Which
> > makes
> > coming on here and bragging about 100% kinda foolish.
> We are not bragging. We are asking you to support the false claims that
you
> make about fiicticious bugs and negative user experiences using our
> products.
>
> After all, aren't
> > there known bugs within the framework itself, which you yourself admit
to
> > using? Particularly the reflection namespaces? In order for your
> > software
> > to be perfect it would mean Microsoft's software would have to be
perfect.
>
> Again, we didn't say anything about perfect, you did. If we use a 3rd
party
> library or part of the framework, we adapt our implementation to avoid it
> and report it to Microsoft or the vendor involved. We have posted several
> Whidbey related bugs to the 2005 feedback center that were confirmed and
> fixed for newer builds of the 2.0 framework.
>
> >
> >> We do not actively search our competitors web sites looking for their
> >> test
> >> cases, but we do notify them directly when we identify issues in their
> >> products.
> >
> > Why not? I would get as much info from my competitors as I could!
> >
> We do the best we can any anyone concerned will let us know if they become
> aware of any actual problem in our software as opposed to the fictitiuos
> statements that you and your friends keep making here. Instead of spending
> so much time creating false propaganda, you could help the developer
> community by posting real bug reports that you detect in the framework or
> our products.
>
> > Oh... sorry... Every time I hear a long winded speech with absolutly no
> > substance to it except for the same thing written *over* and *over*
again
> > I
> > instantly think I have to start clapping at the end.
>
> You should be apologizing to everyone else here whose time you keep
wasting
> by posting these spam messages to this technical forum that require us to
> respond and defend our products against your false claims. For our
benefit,
> yours, and everyone elses here, please stop posting messages that continue
> to waste the time of all of us here. Go ahead and lurk if you like and
> contact us offline, but I don't want to continue to assist you in filling
up
> these newsgroups with non-technical arguments that everyone has to filter
> out to find the technical information that they are looking for. I
probably
> should never have responded to any of you in the first place, except that
> your attacks on us and our products require us to respond to defend
> ourselves and diffuse your intentionally misleading statements.
>
> In short, please write us privately if you feel it necessary, but leave
> these groups to technical discussions that developers here are interested
in
> reading. Some of the other people here have spoken up to discourage your
> inappropriate behavior here, and you have probably scared a few people who
> don't want to have to waste their own time arguing with you, but I'm sure
> that the majority of the people in this newsgroup and the ones reading
this
> thread would like you, Nak, and <a> to just go away from this thread, this
> group, and any news server that they are interested in for it's technical
> content.
>
> Jonathan
>
>

Relevant Pages

  • Re: Decompiler.NET reverse engineers your CLS compliant code
    ... entire developer community reading this thread because they are interested ... > speech over and over about how many bugs you've reported to other ... > there known bugs within the framework itself, ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Towards a responsible vulnerability process
    ... in tremendous improvements in developer education. ... But the best example we have of code that is nearly bug-free is the ... The very best developers create few bugs, ... learn after some number of unpleasant experiences. ...
    (NT-Bugtraq)
  • Re: HEADSUP: ibcs2 and svr4 compat headed for history
    ... That includes kernel interfaces and security bugs. ... The svr4 code was apparently not written ... If we opt to have it off by default, mainstream functionality ... the hard thing to tell from a developer perspective is whether ...
    (freebsd-current)
  • Re: Why has the Metrowerks sign been taken down?
    ... > decisions that need to be made - if every developer wrote up a bug on IB ... time you figure out you can't import menus with IB, ... to wait for Apple to add that feature in response to a feature request. ... reproducible bugs that never should have even been shipped. ...
    (comp.sys.mac.programmer.codewarrior)
  • Re: TDD: Test-Driven Design or Test-Driven Development?
    ... You are allowed to cause friction on USENET - that's what it's for. ... The TDD cycle is very good at preventing bugs, and making the few that slip ... > also be mandated that every developer should document ...
    (comp.object)