If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
Thread Tools | Display Modes |
#33
|
|||
|
|||
Merged AMD-ATI monster embarks on monopoly-busting
"Allan C Cybulskie" writes:
Walter Mitty wrote: "Allan C Cybulskie" writes: .NET is basically a shared library to facilitate application development. And to suggest that application writers should bypass its features and do it all themsleves is (a) incredibly stupid and (b) leads to *even more* bloatware sicne each app would be re-inventing the wheel. Well, let me challenge (a): it might not be incredibly stupid. Whether it is or not depends on how flexible .NET is (how hard is it to massage .NET to doing something that you want to do that is not necessarily standard) and how good .NET is. If .NET is inflexible and buggy, then it is not stupid to bypass it and is instead SMART to bypass it. It's all in knowing what it can do and what you want to do. All SW is buggy to a degree. True enough. But if someone else's libraries are known to be especially buggy -- and I'm not saying .NET IS, BTW -- it might make sense to create your own because if there are bugs in your own code, it is easy for you to change it. It's not that simple when it's the code of another company, as they fix it when they get around to it, which screws over your customers in the meantime. Bleeding obvious. But it does work. We can all pontificate about things in general. THe OP made an unsubstantiated link between a desktop corruption and .NET. Well, from what he saw -- if accurate -- he has good reason to think that there might be a link there. He could, of course, be wrong but so could those who say that .NET just couldn't possibly do anything in any situation to produce that behaviour. Its not that bit thats the issue its the whole "microshaft" crap, and spouting on about .net & com being "dead" etc and accusing ATI of being "lazy". Yawn. As I said earlier, as a designer I've learned that sometimes side effects of what you intended to do can be really, really odd [grin]. As in all things. Millions of people use .net. It is not obsolete. ATI had a reason to use it. The programmers are not "lazy" to use it. And .NET is there to give flexibility and ease application development. It is part of windows. It is not evil. It is there for a reason. The OP should live with it and shut up spouting nonsense. I never supported any of these claims, so this is all irrelevant to what I, personally, challenged in your posts. And the OP has decided to not use .NET since currently he can avoid programs that use it. So Sure he has. it seems like he's living with it as well as you are, since you seem to constantly want to defend it as being GOOD. I don't think you have any Good? I said shared libraries that make application development are a good thing : and dont mistake it for "unnecessary bloatware". more support for that claim than he does that it's bad (and the number of people using it is not sufficient support; they may simply not have the resources to avoid using it). Or the windows kernel. -- Getting your moral direction from politicians is like getting health tips from Keith Richards. |
Thread Tools | |
Display Modes | |
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
Merged AMD-ATI monster embarks on monopoly-busting | AirRaid | General | 79 | August 3rd 06 02:15 AM |
Merged AMD-ATI monster embarks on monopoly-busting | AirRaid Mach 2.5 | Intel | 0 | July 24th 06 11:55 PM |
Merged AMD-ATI monster embarks on monopoly-busting | AirRaid Mach 2.5 | AMD x86-64 Processors | 0 | July 24th 06 11:55 PM |