Comments on: Compiled Web vs. Interpreted Web

By: Earl Colabrese

Earl Colabrese — Sun, 07 Mar 2010 03:40:19 +0000

Hi, I found this article while searching for help with Microsoft Silverlight. I’ve recently switched internet browser from Opera to Internet Explorer 7. Just recently I seem to have a issue with loading sites that use Microsoft Silverlight. Every time I go on a page that requires Microsoft Silverlight, my computer does not load and I get a “npctrl.dll” error. I cannot seem to find out how to fix it. Any aid getting Microsoft Silverlight to function is very appreciated! Thanks

By: Jeremy Chone

Jeremy Chone — Tue, 27 Oct 2009 18:07:33 +0000

@PhilG, I personally think that the Compiled Web is the wrong way for on-demand type of application.

By: PhilG

PhilG — Mon, 14 Sep 2009 20:33:50 +0000

While internet speeds have continued to climb dramatically, it still seems as though the bandwidth is still the single factor that holds back compiled languages on the web. In addition, interpreted scripts are quite easy to create. It still seems like the benefits of a compiled web are years away.

Just my 2 cents
Phil

By: To Flash or to Open Web | Bits And Buzz, by Jeremy Chone

To Flash or to Open Web | Bits And Buzz, by Jeremy Chone — Thu, 25 Jun 2009 15:10:35 +0000

[...] Web applications is usually sub-second responsiveness. As outlined in a previous post about Compiled vs. Interpreted Web, the interpreted nature of the Web makes it very efficient for executing on-demand content & [...]

By: How I got Censored from Techcrunch: L’Arroseur Arrosé | Bits And Buzz, by Jeremy Chone

Thu, 11 Jun 2009 00:58:01 +0000

[...] think I could do 10 times as "well" twice as well. My best content articles, such as “Compiled Web vs Interpreted Web”, average 2,500 visitors in the first 48 hours (which I am very proud of). I will make it a [...]

By: Patrick FArrell

Patrick FArrell — Wed, 10 Jun 2009 17:06:21 +0000

I see a 3rd phase the can coexist with the two you foresee. I anticipate a return to hybrid mainframe (session lives in central computer) and client/server (some horsepower on the client). I see a host of client much dumber than the iPhone that will still want rich communication. I’m not much of an oracle though. Nice analysis.

By: Patrick Farrell

Patrick Farrell — Wed, 10 Jun 2009 17:02:40 +0000

I hate to sound old-fashioned, but I am thinking there’s a 3rd model that represents a return to a hybrid of mainframe and client/server. I’m thinking of devices a lot dumber than the iPhone that will still want to have rich communication. Nice analysis.

By: Oracle on Sun Java, MySQL, OpenOffice, and Linux | Bits And Buzz, by Jeremy Chone

Tue, 19 May 2009 16:14:44 +0000

[...] Bits And Buzz, by Jeremy Chone Technology, trends, and opportunities. « Compiled Web vs. Interpreted Web [...]

By: Jeremy Chone

Jeremy Chone — Mon, 11 May 2009 02:15:55 +0000

@James True, although some good tools like Aptana Studio and Firebug can help too. But true, developer get a best debugging experience with compiled application model.

By: James Ward

James Ward — Sun, 10 May 2009 01:32:13 +0000

Good thoughts Jeremy.

Two major things I like about the compiled web is that compiled languages usually have better debugging and testing tools.

-James

By: Posts about xml as of May 8, 2009 | Shirasmane

Posts about xml as of May 8, 2009 | Shirasmane — Fri, 08 May 2009 14:35:30 +0000

[...] XML API Settings (21 Apr 2009) Javascript Loop through key value pairs from an associative Compiled Web vs. Interpreted Web – bitsandbuzz.com 04/30/2009 Software technologists tend to learn by oscillating . We never arrive [...]

By: Compiled Web vs. Interpreted Web

Compiled Web vs. Interpreted Web — Mon, 04 May 2009 02:44:57 +0000

[...] click here [...]

By: links for 2009-04-30 « My Weblog

links for 2009-04-30 « My Weblog — Fri, 01 May 2009 04:11:36 +0000

[...] Compiled Web vs. Interpreted Web | Bits And Buzz, by Jeremy Chone (tags: web) [...]

By: Topics about Microsoft » Compiled Web vs. Interpreted Web

Topics about Microsoft » Compiled Web vs. Interpreted Web — Fri, 01 May 2009 00:02:08 +0000

[...] Bits And Buzz, by Jeremy Chone created an interesting post today on Compiled Web vs. Interpreted WebHere’s a short outlineSoftware technologists tend to learn by oscillating . We never arrive directly at the right solution; we just come closer to it by going back and forth. We always think (or like to think) that our current solution is correct; only to realize, some years later, that we overshot and need to take a few steps back. The evolution of the software application model is a great example of this syndrome. Every technologist knows about the three main application model phases—Mainframe, Client/Server [...]

By: Ray Cromwell

Ray Cromwell — Thu, 30 Apr 2009 23:59:50 +0000

There’s a video from last year’s I/O on GQuery when it was just a prototype: http://www.youtube.com/watch?v=2ScPbu8ga1Q

The syntax is effectively as terse as jQuery, and prototype extension is simulated rather nicely using generics. As an example:

$(”div.rating”).as(RatingPlugin).rating();

$(”div.heading”).as(Effects).slideDown();

By: Jeremy Chone

Jeremy Chone — Thu, 30 Apr 2009 22:49:13 +0000

@Ray Yes, agree, a JIT like Chrome V8 does not change the nature of the language/application model.

@Ray cool, looking forward to see your video.

More I read your comments on GWT, the more I realize that GWT really leverage the interpreted model very well. Seems to be a very good hybrid solution (although I still do not like the fact to code a Web app the Swing way )

I am a jQuery fan!

By: Ray Cromwell

Ray Cromwell — Thu, 30 Apr 2009 22:38:18 +0000

A JIT cannot optimize code it hasn’t seen. No amount of dynamic optimization will. That is, V8 cannot reduce the wire size of the download. A tool like GWT does dead code elimination, inlining, folding, et al, prior to your browser fetching it. It also can perform capability/browser detection prior to downloading the bulk of the application, meaning that the browser only needs to download the code that is appropriate for it. That’s leaving aside all of the other tool chain benefits you get on large projects when you have early bound namespaces in your language. This has a huge impact for larger applications like a spreadsheet or GMail-like app.

Jeremy, the videos will probably be online.

By: Jeremy Chone

Jeremy Chone — Thu, 30 Apr 2009 21:02:42 +0000

@Chris, Chrome V8 is just a clever JIT. Developers still code in an interpreted mode, and the assembly is still done dynamically on the client side (at runtime). In other word, the whole point of Chrome V8 was to keep JavaScript a dynamic language while reducing the performance gap with compiled languages. Chrome V8 is just go a step further in enhancing the performance of scripting languages.

By: Chris Ryland

Chris Ryland — Thu, 30 Apr 2009 20:55:22 +0000

The trend is for Javascript in the browser to be compiled (witness Google Chrome’s V8 engine), so the compiled/interpreted split doesn’t really make sense in the long run.

By: Jeremy Chone

Jeremy Chone — Thu, 30 Apr 2009 20:07:30 +0000

@Ray Yep, agree with your points.

Google I/O is $300, almost an iPhone or Kitesurf Board. So, I will pass and go Kitesurfing this day.

Developer events should be $49.99 including beer and pizza.