Loose-typing brings a lot of things to the party - allowing approaches to problems that are otherwise difficult to solve. Take linq as an example. Traditionally one of the bottlenecks in applications - esp distributed or loosely coupled applications is data-processing. Paradigms such as DI and AOP are far easier with interpreted languages than with compiled.
Compiled tends to be tied to a platform but performs better, interpreted achieves platform independence at the expense of speed. The only exception I'm aware of is SQL which is a special case :) MVC facilitates RAD & prototyping and is a suitable approach for "dumb" UI's (ie web) - but it's not as suitable for desktop driven, service or daemon applications (you wouldn't use an MVC pattern for coding a database or for a control application for your car engine). MVC also brings something to the mix that I think is often overlooked - scaffolding. A more appropriate question you should be asking as a software engineer is - which pattern is suitable for the application I'm developing... :) On Mon, 21 Sep 2009 21:02:51 +0200, Tom Boutell <[email protected]> wrote: > > I've thought about this too. But C++ is full of scary dangerous > backwards compatibility systems-programming-oriented features that > make safe programming harder and make little sense in a web > application. > > I think your argument makes more sense if you're talking Java (or C#) > vs Ruby and PHP. > > A more interesting question is: "if we're going to use MVC frameworks > anyway, do we still gain anything worth having by using loosely typed, > interpreted languages like Ruby and PHP? Assuming for a moment an > equally good framework implementation following the same design > philosophy in the case of each language?" > > Yes, I think we do. Java is still considerably more verbose as a way > of getting your application logic coded. But there are interesting > Java framework-based implementations of Rails-style sites that aren't > *too* verbose: > > http://www.theserverside.com/news/thread.tss?thread_id=32723 > > On Sep 21, 9:28 am, pcummins <[email protected]> wrote: >> With the introduction of PHP frameworks and widespread use of MVC >> pattern in web development, has anyone ever wondered why we aren't >> simply writing our web applications in C++, and using 'templates' >> files for view delivery? >> >> It seems like a pretty interesting cycle. >> >> Internet begins >> High level languages aren't easy enough for newbies to write websites >> Scripting languages (php,ruby,python) are created and take hold of web >> market >> Enterprise level applications require standardization of programming >> techniques >> Scripting languages get standardized with frameworks >> Frameworks are entirely oo, and MVC ensues >> Programmers wonder why they ever stopped writing in C/C++. >> >> I love what Symfony (and other frameworks) have done for PHP. I also >> love the flexibility and loosely typed nature of PHP, but sometimes I >> wonder.... how far away is a good PHP framework from C / Java? >> Imagine the performance gain of not having to deal with PHP. I guess >> this is kind of the vision of .net. >> >> What are your thoughts? > --~--~---------~--~----~------------~-------~--~----~ > You received this message because you are subscribed to the Goog --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "symfony users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/symfony-users?hl=en -~----------~----~----~----~------~----~------~--~---
