Creating .NET C# Applications for Linux
An anonymous reader wrote to mention an article on the IBM site entitled Mono brings .Net Apps to Linux. From the article: "Mono gives open source developers the programming power and flexibility to build applications for Linux while maintaining cross-platform capabilities, using a variety of .NET-compatible languages. One of the great advantages of Mono for current .NET developers is providing an easier migration path to Linux. The Mono project has a very open and active development community and provides both developer tools and the infrastructure needed to run .NET client and server applications. Perhaps the most important benefit of using the Mono architecture is that you gain language independence. Mono lets you leverage any existing code from languages supported in the .NET runtime. "
Javascript/AJAX is an awesome combination. Scripting languages provide very awesome RAD, whilst using a web browser + javascript + xmlhttprequest provides a very smooth professional appearance to your application. .Net and ASP .Net are cool, but my personal experience is that development times tend to be quite long, compared to the same application in Javascript/XMLHttpRequest.
.Net provides web form widgets that work along similar lines to VB forms elements. However, plain old html is much easier to work with, more dynamic and more flexible than VB-type widgets. The .Net widgets do provide the illusion that the application is client-based, but AJAX does this too, and is much easier to use. ASP .Net provides a form editor but it tends to work uneasily with custom-edited HTML.
One issue is variable declaration. Declaring a variable as an XMLElement rather than simply typing var takes a half second or so longer each time. Certain results need to be cast to be useful, for example, SelectSingleNode often needs to be cast into an XMLElement. You can't easily write a function that can handle many datatypes, and the datatypes tend to be purvasive throughout your project, difficult to change, at least without using typediffs, which has its own overhead.
ASP
Javascript/XMLHttpRequest rock totally. They provide the separation of display and code that ASP.Net provides. They're lightweight, readily maintainable, easy to read, and very flexible and powerful.
Obviously, it would be unwise to state that AJAX is the best solution for every scenario, but it's certainly a highly optimal solution for a wealth of functional, technical and user specifications. So much so that Microsoft is currently trying to move ASP.Net to use AJAX, the Atlas project!
Hugh