|
hope not, asp.net sucks IMO. dont get me wrong I love C# and use it everyday, but it is almost there. its still a young platform. give it time, it will come around.
/bb|[^b]{2}/
|
|
|
|
|
Well.. I was more thinking about WinApp and WebApp, not the language.
I was meaning that there will be more and more of WebApp than WinApp.
By the way... ASP.NET can be used with any language.
Presently I code in C#
If someone says "Die mortal!", don't stay to see if he isn't.
|
|
|
|
|
I hope not! The WebApp concept is fine for a few applications but not for most general purpose ones like an Office Suite... Can you see someone using a Web based CAD or drawing application?
Thin clients are ok for simple things like data entry, but lack the power and are to slow for most applications.
There are to many examples of applications where the .NET framework can only ever be used as a wrapper layer...
MHO
|
|
|
|
|
I think dotnet (well I am also referring to VS.net) is very slow. We have been working on 1.8 GHz machines with 512 MB ram and it is deadly slow, specially for debugging a desktop application and WinForms controls. I am a C++ programmer and just love application performance issue by nature. I never thought .net will make it (comparing to the huge effort Microsoft is doing) since its first beta, but I could be wrong. By the way, I dont like Java too.
|
|
|
|
|
Worse, .NET apps eat memory like crazy. And unfortunately, you can't really tell your customers: memory is cheap these days - why don't you buy yourself a Gig or two of RAM?
My programming blahblahblah blog. If you ever find anything useful here, please let me know to remove it.
|
|
|
|
|
I think M$'s thinking is to make programs run bad on good machines so people will still have to buy new computers to get a speed advantage. I mean look at their OS's...every "improved" version was designed to only work on good computers of the time.
|
|
|
|
|
IMHO No, because the masses don't have .NET is not a valid option, since the question is Is .NET ready for the masses and not Are the masses ready for .NET.
Regards
Thomas
Disclaimer:
Because of heavy processing requirements, we are currently using some of your unused brain capacity for backup processing. Please ignore any hallucinations, voices or unusual dreams you may experience. Please avoid concentration-intensive tasks until further notice. Thank you.
|
|
|
|
|
You can't run .NET if you don't have the .NET framework on your machine. So why is that not a valid option?
An expert is somebody who learns more and more about less and less, until he knows absolutely everything about nothing.
|
|
|
|
|
Navin wrote:
You can't run .NET if you don't have the .NET framework on your machine.
But in this case it's me (or at least my machine) who isn't ready.
Regards
Thomas
Disclaimer:
Because of heavy processing requirements, we are currently using some of your unused brain capacity for backup processing. Please ignore any hallucinations, voices or unusual dreams you may experience. Please avoid concentration-intensive tasks until further notice. Thank you.
|
|
|
|
|
Ahem, ASP.NET, only the server needs the framework.
Signature under construction.
|
|
|
|
|
Well, to *run* ASP.NET you surely do. But only web servers actually run ASP.NET. The rest just load up pages in browsers and don't know that it's .NET or whatever rendering the pages. 
An expert is somebody who learns more and more about less and less, until he knows absolutely everything about nothing.
|
|
|
|
|
Thats why I said only the server needs the framework.
Signature under construction.
|
|
|
|
|
Did somebody use obfuscator products with success at the first time?!?
Alberto Bencivenni
www.devDept.com
|
|
|
|
|
I'm lucky that my apps aren't mass-distributed, so I don't have to worry about obfuscating my source-code.
I wonder whether or not it is worth it. Are we not passed the stage where all the value is in the source-code and to a stage where it is the knowledge of the developers, the support we give our product, our expertise in solving problems that is more valuable to a company?
Michael
CP Blog [^]
|
|
|
|
|
And what is the value of being able to see the source of 90% of applications out there? The good stuff is patented, the rest is connector code we write everyday ourselves anyway.
regards,
Paul Watson
Bluegrass
South Africa
Christopher Duncan wrote:
"I always knew that somewhere deep inside that likable, Save the Whales kinda guy there lurked the heart of a troublemaker..."
Crikey! ain't life grand?
|
|
|
|
|
You would also have to consider any software where transactions are worth money - you don't want people being able to poke their nose into the details of that too easily.
Gavin Greig
"Haw, you're no deid," girned Charon. "Get aff ma boat or ah'll report ye."
Matthew Fitt - The Hoose O Haivers: The Twelve Trauchles O Heracles.
|
|
|
|
|
You make a good point Gavin. Hopefully though most financial software has it's core functionality on the server side behind thick security making reverse engineering difficult.
regards,
Paul Watson
Bluegrass
South Africa
Christopher Duncan wrote:
"I always knew that somewhere deep inside that likable, Save the Whales kinda guy there lurked the heart of a troublemaker..."
Crikey! ain't life grand?
|
|
|
|
|
Yep, it would be a bit bad if obfuscation was the only weapon in the arsenal. However, there are circumstances where it's not possible to rely on server-side security - the simplest and most widespread one I can think of would be shareware or other try-before-you-buy software, where the act of registering has a financial value.
We all know things like that are crackable if someone cares enough, but it's probably still worth using obfuscation to deter casual tinkering.
Gavin Greig
"Haw, you're no deid," girned Charon. "Get aff ma boat or ah'll report ye."
Matthew Fitt - The Hoose O Haivers: The Twelve Trauchles O Heracles.
|
|
|
|
|
I would hope so, too, althoguh interestingly enough, Microsoft itself has historically gone through great pains to protect its source code, but now invents .NET which makes it pretty simply to reverse-engineer, reflect, or whatever and effectively get the soruce code from .NET apps.
An expert is somebody who learns more and more about less and less, until he knows absolutely everything about nothing.
|
|
|
|
|
I know that we are not the main stream, be making our source code available woudl do much more harm than good.
we are here to help each other get through this thing, whatever it is Vonnegut jr.
sighist || Agile Programming | doxygen
|
|
|
|
|
To qualify, when I voted Yes I meant ASP.NET. I don't have much experience in desktop apps and so cannot comment on .NET for that (though we do some Windows Services and they are bloody brilliant in .NET compared to the hoops I had to jump in VB6).
It seems all these .NET polls need to be qualified alongs the lines of ASP.NET vs The Rest of .NET. Anyone who knocks ASP.NET needs a head check.
regards,
Paul Watson
Bluegrass
South Africa
Christopher Duncan wrote:
"I always knew that somewhere deep inside that likable, Save the Whales kinda guy there lurked the heart of a troublemaker..."
Crikey! ain't life grand?
|
|
|
|
|
ASP.NET is the best web development tool I've come across (and I've tried the lot). Of course I still don't think web-applications are ready to replace desktop applications for the masses, but thats a totally different issue and probably another poll.
I like building desktop apps in .NET and C#. Actually, I'll qualify that, I like building .NET apps using C# and MyXaml[^] because I still think code-based forms are a bad idea.
I certainly think .NET is good enough to produce solid applications for the desktop masses, although I still think the tools need another release before they match what we've been building in MFC. The platform won't start to mature until we start getting apps out to the users and find out what works in the real world and what doesn't.
Michael
CP Blog [^]
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
