If more and more software developers are going to be developing browser-based applications using technologies such as JavaScript, Flash, and AJAX, we will need to see the Web browser become a much more capable platform. In short, the browser will need to duplicate much of the work that has been done over the years in the operating systems field.
JavaScript has been around for over a decade now. During that time, we’ve seen it implemented by every major browser vendor, and thus we’ve seen it become widely used by many Web sites. We’ve even seen JavaScript used in non-Web applications and uses.
But JavaScript has some pretty serious drawbacks. The performance of the various JavaScript interpreters embedded in the popular Web browsers has always been less than ideal. And being interpreted, it often becomes more difficult to detect syntax errors and other common mistakes. Worse yet, being weakly typed opens JavaScript scripts up to a whole host of type-related problems.
KDE 4.0 was released several days back, and thanks to the KDE Four Live CD, I was able to give it a try with very little effort. Having used it for about a day and a half now, I’d like to share some of my impressions of this new release of KDE. Specifically, I will be focusing on the Konqueror 4.0 Web browser. But please keep in mind that I have not performed any formal studies or benchmarking, and what follows is merely my opinion.
When it comes to purchasing consumer-grade PCs these days, it’s rare to find a system with a CPU that only has a single core. Most laptops even offer a dual-core CPU. So as software developers, we’re entering a unique era where we can start to employ parallelism in ways that would not have been practical before. In some cases, we will need to exploit this parallelism if we hope to increase the performance of our software.
I read today a blog article about the greatly-increased complexity of ECMAScript 4, relative to earlier versions. Indeed, the number of features is quite staggering. And the first thing it made me think of was C++.
C is a relatively small language. That’s understandable, considering it was initially developed for system-level programming on computers with rather minimal resources. Soon enough, Stroustrup and others developed C++, adding a variety of higher-level constructs to C. Over time, C++ has grown to be a rather complex beast.
GIMP 2.4 was recently released. Although I do very little image manipulation, GIMP is one of the more widely used open source applications, thus I like to keep up to date with its developments.
One of the first things I went to check out after reading of the release was the screenshots section of their web page. I have to say, it was a very disappointing experience.
Based on this article, it sounds to me like Douglas Crockford, of JSON fame, has realized the pathetic state of Web-based application development. It was quite refreshing to see an architect at a major Web firm (Yahoo!, in this case) point out the numerous and obvious flaws when using Java applets, JavaScript, XML, CSS, HTML, and AJAX for application development.
Several days back, Opera 9.50 Alpha was released. For the time being, you can read more about the new features in Opera 9.5. Some of the notable enhancements include a better ECMAscript engine, improvements to the layout algorithm, faster font rendering, and a more responsive UI.
Earlier today I was reading an article about Parrot. Parrot is, as stated on the project’s Web site, “a virtual machine designed to efficiently compile and execute bytecode for dynamic languages. Parrot currently hosts a variety of language implementations in various stages of completion, including Tcl, Javascript, Ruby, Lua, Scheme, PHP, Python, Perl 6, APL, and a .NET bytecode translator.”
Today, thanks to this article, I saw a very telling diagram giving an overview of the “Mozilla Platform”. Before you read on, I encourage you to study the diagram for a few moments.
