Angel Blog Reviews » firefox

New Firefox Release…One Last Time?

cgseo — Mon, 11 Jan 2010 15:30:00 +0000

As we reported last week , Firefox's latest version of 3.6, release candidate 1, has been released to the general public . This time around, however, Mozilla has issued a more general release, as the new version will not only be available for download but also part of an automatic update for those already running Firefox. The release is one more sign that we're getting closer by the day to a full-on sparkly new version of Firefox. For those of you worried about updating, Mozilla has assured us that "over 75% of the thousands of Firefox Add-ons have now been upgraded by their authors to be compatible with Firefox 3.6," so go ahead and take that leap. But what will you find on the other side? Sponsor Firefox 3.6 RC1 Features In addition with offering this release as an automatic update, Mozilla has offered a synopsis of what it sees as the most important new features to be found in what the company hopes to be a near final version. Users can change the browser's appearance with a single click using Personas . Firefox 3.6 alerts users about out of date plugins to keep them safe. Changes to how third-party software integrates with Firefox to increase stability. Improved automatic form fill provides better options from your form history. Open, native video can now be displayed full screen , and supports poster frames . Support for the WOFF font format. Improved JavaScript performance, overall browser responsiveness and startup time. The ability to run scripts asynchronously to speed up page load times. Support for the HTML5 File API Support for new CSS, DOM and HTML5 web technologies. While wallpapering Firefox with the latest blockbuster movie may be an attractive addition, we are looking forward to a faster and more stable Firefox. Loading scripts asynchronously should speed up some page load-times dramatically by letting faster scripts run while slower ones continue to do their work in the background - something our computers have been doing for a long time now. And the changes to third-party software integration should offer a huge boost to the browser's stability by keeping the core components of the browser safe from being modified. For the web developers out there, increased support for CSS, DOM and HTML5 is always a welcome addition, and the addition of the WOFF font format may further help page load-times and give web designers a greater range of choice. Discuss

Read more here:
New Firefox Release...One Last Time?

MailBrowser: Get More Out of Your Google Contacts

cgseo — Wed, 06 Jan 2010 17:57:03 +0000

MailBrowser wants to make Gmail and Google Apps more useful by offering a consolidated view of all your contacts and attachments in a browser sidebar. In this sidebar, you can quickly search for contacts, see the latest emails you received from a specific contact, add calendar events and attach notes and tags to a contact. In many respects, MailBrowser looks a lot like Xobni for Gmail. Sponsor Features MailBrowser is currently only compatible with Internet Explorer and Firefox on the Mac (OSX 10.5 and higher) and Windows, though the team is working on Safari and Chrome versions as well. The plugin offers a rich set of features , including support for multiple Gmail and Google Apps accounts and rich previews of attachments. Another nice feature is the "trend" section that appears at the bottom of the sidebar. Here, two graphs show a timeline view of how many emails you sent and received from any given contact. MailBrowser stores all your data locally on your hard disk, so no information is ever shared with the service. Because all the data is stored locally, MailBrowser also keeps a copy of all your attachments on your machine. The application also syncs all the data back to Google Contacts in the cloud, so any changes you make on one computer will automatically appear on another machine. Xobni for Gmail In many respects, MailBrowser is very similar to Xobni - a popular Outlook addon. Xobni, however, puts a stronger emphasis on giving you additional information about a contact by looking at the contact's social networking profiles. MailBrowser plans to add this functionality in a future version . Currently, the service can only display details about a contact's domain and website. More Features Coming Soon MailBrowser has big plans for the future. The company plans to offer support for more services (Yahoo Mail, Live Mail, etc.), integration with enterprise apps like Salesforce and integration with social media services like Facebook, LinkedIn and Twitter. Verdict For now, MailBrowser works just as advertised. It doesn't yet offer the rich feature set of Xobni, but the company is clearly working on that. If you have a very large mailbox, it can take a while for MailBrowser to download and index your information. Luckily, the download process starts with your most recent email, so that you can be up and running long before your last email has been downloaded. Discuss

Continue reading here:
MailBrowser: Get More Out of Your Google Contacts

Firefox 3.6 RC1 Released

cgseo — Wed, 06 Jan 2010 16:16:51 +0000

Mozilla has made the first release candidate for Firefox 3.6 available for download this morning, following a recent announcement that further releases would be delayed. Firefox 3.6, codename "Namoroka" , looks to improve startup time and general responsiveness , among other issues. Sponsor For those of us who aren't in the know about software versioning, as a "release candidate", Mozilla is hoping this is what Firefox 3.6, without the asterisk, is going to look like. "Should everything run smoothly during testing this is what will be released to our users as the official version after a beta period," reads the description on Mozilla's development wiki . Downloads are available for Windows , Mac and Linux from Mozilla's FTP site. Discuss

Visit link:
Firefox 3.6 RC1 Released

Become a Test Pilot: Mozilla Wants Your Help To Make Firefox Better

cgseo — Sun, 27 Dec 2009 16:00:00 +0000

If you want to help Mozilla to make Firefox better but you are not a developer, here is your chance. Earlier this year, Mozilla announced the launch of Test Pilot , the organization's new distributed usability lab. Test pilots will be enlisted in various usability tests and will be some of the first to see some of Mozilla's ideas for new user interfaces and Mozilla Labs products. We first wrote about Test Pilot when it was just a "still-in concept platform." Now, however, you can download the Test Pilot add-on for Firefox 3.5 here and begin to help Mozilla make Firefox even better. Sponsor Editor's note: This story is part of a series we call Redux, where we'll re-publish some of our best posts of 2009. As we look back at the year - and ahead to what next year holds - we think these are the stories that deserve a second glance. It's not just a best-of list, it's also a collection of posts that examine the fundamental issues that continue to shape the Web. We hope you enjoy reading them again and we look forward to bringing you more Web products and trends analysis in 2010. Happy holidays from Team ReadWriteWeb! First Tests Are Coming Soon For now, Mozilla will start the program with a survey that aims to get a better understanding of who is joining the Test Pilot community. The first actual tests should arrive soon after this first survey is complete. Mozilla stresses that it will take its users' privacy seriously. Participants have to opt-in and data will be stored in anonymous form. Only aggregate test data will be made available to the public. Overall, this looks like a great project. Usability studies tend to be slow and costly, yet with Test Pilot, Mozilla will be able to quickly enlist feedback about new design ideas from its large community of users. Discuss

The rest is here:
Become a Test Pilot: Mozilla Wants Your Help To Make Firefox Better

Opera Feels The Need for Speed: Releases First Pre-Alpha of Opera 10.5

cgseo — Tue, 22 Dec 2009 15:00:19 +0000

Opera just released the first pre-alpha version of Opera 10.5. While most users generally only think about Firefox, Internet Explorer and Chrome as the major players in the current browser wars, there can be no doubt that Opera is working hard to push browser development forward as well. This latest alpha version shows that Opera has worked hard to speed up the browser. Carakan , the new JavaScript engine in Opera 10.5, is up to 7 times faster than Opera's current engine. The new version of Opera also adds a number of new features like an enhanced private browsing mode and a new graphics engine that can be hardware accelerated. Sponsor The new alpha is currently only available for Windows and OSX users - a Linux version will follow soon. Download links can be found at the bottom of this page . New Features New Features: private browsing better integration with native systems notification messages are now non-modal improvements to the search box and the address box new and improved highlighting new inline page search and password manager Besides the focus on speed - an area where Opera used to lead before WebKit based browsers like Safari and Chrome became popular - the company also included a number of other enhancement in this early version of 10.5. Windows 7 and Vista users, for example, will notice that the browser is now closely integrated with the desktop environment and makes use of features like Aero Glass in Vista and Aero Peek and Jump Lists in Windows 7. On the Mac, Opera can now make use of multi-touch gestures like the 3-finger swipe and Growl notifications. Other new features include a new "private tab" and "private window" mode that actually works far better than similar features in other browsers. You just have to right click on the tab bar and select "private tab" to start the private browsing mode in this new tab, for example. Opera also updated the look and feel for the browser's inline page search and password manager. It's All About Speed The focus here for Opera, however, is clearly not so much on bringing new features to the browser (the current Alpha doesn't even support O pera Unite , for example), but on testing the new JavaScript engine. When we spoke to Opera's CEO Jon von Tetzchner about the state of the browser during LeWeb earlier this month, he stressed that the company was very focused on improving the speed of the browser. He did stress, however, that the JavaScript engine was only a small part of this effort and that the company was also looking at other bottlenecks that are slowing the browser down. The fact that that new image rendering engine is already pre-wired for hardware acceleration is a good example for this (though the feature isn't turned on yet). We will bring you more of our interview with von Tetzchner after the holidays. In our own tests, Opera performed remarkably well and this new version clearly shows that it would be unwise to underestimate Opera in the browser wars. We should note, however, that this is still a very early alpha version and that the browser is likely to crash occasionally. Discuss

Read more from the original source:
Opera Feels The Need for Speed: Releases First Pre-Alpha of Opera 10.5

Meet the 12 Lucky Browsers European IE Users Will Be Shown Next Year

admin — Mon, 21 Dec 2009 21:02:22 +0000

As part of the European Union's antitrust agreement with Microsoft , the company will be required next year to show a list of alternatives to Internet Explorer to any Windows user with IE installed as their default browser. Love or hate the government intervention, it's notable to see which browsers are about to get a big boost in user numbers. The EU says increased viability in the browser market will lead to more competition and more innovation. Here are the companies that will get a first crack at new levels of market viability in Europe. Sponsor On the Front Page - The Best Known 5 The first page of the Choice Screen, which users will be presented with when they first turn on their computers or when they click a link for it later, will feature whichever five browsers have the largest market share over the previous 6 months. Microsoft will begin showing the page to users in March, 2010. Right now the top 5 will include, in the order listed on an EU page about the program: Apple Safari - that's right, even for Windows! Google Chrome - so soon. If Chrome can grow so fast, it makes you wonder if government intervention is really needed. Of course, Chrome has been promoted prominently on Google pages. That could become part of the next antitrust issue. Microsoft Internet Explorer - gets better all the time, even with dominant market share. Couldn't the EU just require people to stop using IE 6? Mozilla Firefox - the classic that's most effectively challenged IE. In fact, it's done so pretty effectively. Too bad Chrome now runs circles around its performance. Opera - loved by mobile users, loved by Europeans. Below the Fold - The Smaller Challengers Users will be able to scroll the Choice Screen horizontally and see the next 7 most popular browsers at the time. Here's who the EU lists as those browsers today. AOL - chuckle if you will, but AOL is doing a lot of innovative work with social networks and lifestreaming these days. Maxthon - is a popular browser in China and has its sights set on topping Opera in Europe. K-Meleon - says its a super-fast Windows browser built on Gecko, the same layout engine Firefox uses. Flock - is a Mozilla-powered browser that integrates a whole lot of social features. It's got such a great feature set that we recently asked Why don't you love Flock? Avant Browser - says that it, in fact, is the browser that's the fastest. It includes an inline RSS reader and a number of other interesting features. Sleipnir - is a highly-customizable browser that says it's big in Japan. Slim Browser - a Windows browser focused on automating processes. That's the field, so far! Do you think this move will foster increased innovation? Do you think it's needed? Discuss

Read the rest here:
Meet the 12 Lucky Browsers European IE Users Will Be Shown Next Year

Firefox 3.5 Takes the Top Spot Worldwide

cgseo — Mon, 21 Dec 2009 19:29:00 +0000

Firefox hit a new milestone today, as version 3.5 overtook Internet Explorer 7.0 with nearly 22% of the browser market, according to statistics from web analytics service StatCounter . This comes on the heels of statistics we saw earlier this month , which showed Firefox overtaking IE for overall usage in Germany. Sponsor While IE still dominates the browser market - with 55% of people using some version - all combined versions of Firefox occupy 32% and have been steadily gaining ground. Released at the end of June, version 3.5 of Firefox has quickly climbed the charts. IE 8, on the other hand - which was first released in beta more than a year earlier, with a full release in March 2009 - now holds a similar 20% of the market to that of Firefox 3.5's 22%. It would seem that a majority of Firefox 3.5 users were already using 3.0 and upgraded, as the 20% drop in 3.0 use almost directly correlates to the 22% increase in 3.5. Discuss

See the article here:
Firefox 3.5 Takes the Top Spot Worldwide

Kynetx: Powerful Cross-Platform Tool for Creating Firefox, IE & Chrome Extensions

admin — Mon, 21 Dec 2009 18:59:33 +0000

Kynetx offers developers a single platform for building extensions for multiple browsers. Developers write their code in Kynetx's own rule-based language and the service builds the actual extensions. Originally, Kynetx only supported Firefox and Internet Explorer, but a few days ago , the company also announced support for Google Chrome. Thanks to this, developers can now use Kynetx's AppBuilder tool to build and deploy custom extensions for the three top browsers that offer a built-in plugin architecture. Sponsor For now, of course, only the Windows version of Chrome supports extensions, but extension support for the OSX and Linux version is scheduled to arrive soon. Kynetx is a universal browser extension that has a few similarities to Greasemonkey . The programming language for the extension is the Kynetx Rule Laguage (KRL) and the company offers an online editor for writing apps on top of Kynetx. We should note that Kynetx doesn't allow users to build every type of extension. The system is best suited for building plugins that add additional information to a website. Kynetx's extensions use Action Cards to augment these sites with additional information. One example for such a plugin is this app that reminds users when a company offers a discount through AAA. For some more details about the company, have a look at this video interview Robert Scoble did with the company's founder and CTO. The company also offers a good tutorial and documentation here . AppBuilder Tour View more presentations from knightfour . Discuss

View original post here:
Kynetx: Powerful Cross-Platform Tool for Creating Firefox, IE & Chrome Extensions

RSS Reader Market in Disarray, Continues to Decline

admin — Mon, 21 Dec 2009 04:04:35 +0000

One of the interesting trends of 2009 has been the gradual decline of RSS Readers as a way for people to keep up with news and niche topics. Many of us still use them, but less than we used to. I for one still maintain a Google Reader account, however I don't check it on a daily basis. I check Twitter for news and information multiple times a day, I monitor Twitter lists, and I read a number of blogs across a set of topics of most interest to me. Frankly I'm more likely to use Google Reader to search for specific information nowadays, than to scan my subscribed feeds for their latest posts [I should note however that our news writers use a variety of RSS Readers daily]. So what's happened to RSS Readers. Do people still use them and is there still a viable market for them? Sponsor In February 2007 we reported on the state of the RSS Reader market, based on statistics from Feedburner and Pheedo. At that point Google had 59% market share amongst web-based RSS Readers, followed by Bloglines with 33%, then Newsgator and Netvibes with 3% (note: this didn't count Newsgator's desktop apps, like FeedDemon). Pheedo's stats in February 2007 were somewhat different: Newsgator Online had 27% share, followed by MyYahoo! with 20%, Blogines 19% and Google Reader 13%. The first time ReadWriteWeb looked into market share for RSS Readers was 5 years ago, in December 2004 . At that point, very early in the web 2.0 era, Bloglines was the clear leader and Google Reader wasn't even a glint in the milkman's eye. 2009 Update on RSS Reader Market Well, unfortunately Feedburner no longer publishes any useful data about RSS Readers. The product has been infrequently updated since Google acquired it in June 2007 and it no longer even has a proper blog (a Google blog called Adsense For Feeds was the closest I could find). Pheedo also has gone quiet from a blogging perspective - its last blog post was January 2009. Tellingly though, it has an active Twitter account . The best data we have then is ReadWriteWeb's own Feedburner account. Here is the top 10 for Dec 09: 1. Google Feedfetcher 85665 (includes both Google Reader and its start page iGoogle) 2. Bloglines 38797 3. Netvibes 34894 4. FriendFeed 16269 5. NewsGator Online 6753 6. Firefox Live Bookmarks 2999 7. PostRank 2454 8. Windows RSS Platform 1587 9. Mac OS X RSS Reader 1307 10. Zhuaxia 1127 (a Chinese RSS Reader) Feedburner's numbers always need to be taken with a large grain of salt, nevertheless we can see that Google is now over twice the number of Bloglines. There's little sign of life on Bloglines' blog either and its Compete.com traffic numbers show a decline since June 2009 . Netvibes, FriendFeed, Newsgator and PostRank are the only other english language competitors showing in our Feedburner numbers. The others are either browser (Firefox) or operating system readers. Also note that Newsgator shut down its online RSS Reader at the end of July this year. Conclusion: Google Dominates, RSS Readers Less Relevant These statistics are by no means the definitive RSS Reader market numbers. They do clearly show two things though: 1) Google now dominates what's left of the RSS Reader market. Bloglines is hanging in there, but it seems like it's given up the fight judging by lack of activity in its blog and traffic dips. 2) RSS reading is a very fragmented experience circa 2009. People can monitor news and information via Twitter, Facebook, start pages like Netvibes, their Firefox bookmarks, their OS, aggregators like Techmeme, and so on. Tell us in the comments how you currently read your RSS feeds and how often you check them in an RSS Reader - if indeed you still use one... Discuss

Visit link:
RSS Reader Market in Disarray, Continues to Decline

Server-Side Javascript: Back With a Vengeance

admin — Fri, 18 Dec 2009 00:25:44 +0000

Last month was Javascript season in Europe, with two conferences dedicated to the language that powers interactive web applications, and a third , which featured it heavily. If a common theme emerged, it was the buzz about Javascript leaping out of the browser to serve other domains, and the noise has only become louder in the aftermath. Of all the applications outside the browser, server-side Javascript is the most alluring for reasons described in this post. An idea that would have had you laughed out of the room a few years ago is edging towards reality. Sponsor Javascript outside the browser? Some of the applications are graphical user-interface platforms similar to the browser, e.g. Adobe Air, television sets. With other applications, there's not even a graphical user interface. For example, some have suggested using it as a general-purpose Unix scripting language. This guest post was written by Michael Mahemoff , who works at Osmosoft as lead web developer and blogs regularly for Ajaxian and on his his personal blog, Software As She's Developed . You can follow him on Twitter . The Perfect Storm Server-side Javascript isn't a new phenomenon; Netscape stuck Javascript in the server way back in 1996, right after they introduced it to the world as a browser technology. Interest soon waned, and the language was confined to the browser for the most part. Even there, it didn't get a whole lot of respect and was frequently dismissed as a hack language capable of no more than annoying alert boxes and gratuitous ticker tape animations. But suddenly, serious web-based applications started sprouting up. GMail, Google Maps, and JotSpot (kind of a Google Docs predecessor) were all running inside the browser. They weren't supported by Flash, nor ActiveX, but Javascript manipulating the browser's Document Object Model (DOM). The term "Ajax" was coined to describe these applications, and a community flourished. A few years on, Javascript has become the world's most popular programming language by some accounts. Not so surprising when you consider its special status as the standard language shipped with all major browsers. It's the web's lingua franca. While most web developers have a favourite, primary, language for server-side work, they converge on Javascript when it comes to the browser. Javascript today can be compared to the English language: it's arguably the most popular language as long as you count basic competency, not just outright fluency. Given that you're already using it in the browser, why not stick it in the server too? One language all the way down makes it easier for a single programmer to work on either side of the wire; there's less of a mental shift. For project managers, the trend would make it easier to move developer resources between the front end and the back end if a common language is used on both. Many in the developer community now recognize Javascript as a respectable language, with understood patterns for effective use. In fact, many of Javascript's negatives were a case of misdiagnosis: the problem was really the browsers' DOM (Document Object Model) APIs, not the language itself. Take those out of the equation and you're left with a solid language capable of tackling diverse problems. There's also a promising reuse story for this "dual-side Javascript" scenario. Take form validation for example. Right now, it's common to write the same logic in two different languages. In Javascript, you write a validator to give the user immediate feedback inside the browser, and in a language like PHP, you write a validator to ensure data integrity once the form data has been uploaded to the server. But once you switch to Javascript on the server, you just need to write a single validation routine at both ends. Under some styles of development, you can also arrange for a function in the browser to directly call another function inside the server; the code is smaller and simpler to write, not being bogged down in the technical details of transferring data across the network. Javascript performance has also moved forward in leaps and bounds, thanks to browser competition. Firefox's Javascript engine, Spidermonkey, increased in speed by a factor of 20-40x . Safari's underlying engine - Squirrelfish, aka Nitro - posted similarly impressive gains (see chart below), and Google Chrome came on the scene last year along with its highly optimized V8 Javascript engine, a very real contender in the "fastest Javasript engine" stakes. Server-side Javascript also dovetails nicely the new breed of NOSQL databases . Being web-native, these databases tend to communicate in HTTP, and in some cases JSON (JavaScript Object Notation) is the message format. Javascript libraries already include support for exactly that kind of interaction and programmers are familiar with them. Some of these NOSQL systems go beyond data persistence and into the zone of full-fledged Javascript application environments. Next page: Towards A Mature Server-Side Ecology Towards A Mature Server-Side Ecology In the simplest case, all you need to run server-side Javascript is a Javascript engine to plug a web server into. There are plenty of open source options here; the choice will come down to the language its implemented in, which affects the kind of environments it can run in, in addition to the usual factors like performance and level of support. Many Javascript platforms run on the Rhino engine for example, and Rhino is built in Java; this means that they can easily integrate with Java components. Thus, you can build the entire user-interface in Javascript - including a thin UI layer on the server - and still have it backed by a conventional enterprise Java stack. Helma is one prominent example of this architecture. Once equipped with a Javascript engine, you can write simple CGI scripts as you would with any other language - read the request, write the response. In practice, you'll also want good library support to get anything useful done. Some environments do come with libraries, and you can also make use of existing libraries developed for browser-based Javascript. What will really make the biggest impact, though, is industry-wide standardisation. To that end, there's a strong grassroots movement underway to converge on a complete API: CommonJS is defining an API for file access, networking, unit testing, and so on, as well as declaring how these components should be packaged for easy import. Multiple efforts are implementing the nascent spec in several major Javascript engines (Rhino, Spidermonkey, V8, EjScript). One open-source platform complying with CommonJS is Narwhal . It has considerable momentum and runs on several of the Javascript engines. CommonJS is raising the level of abstraction for server-side Javascript and allowing developers to use patterns familiar from high-level servers in other environments. Writing a web server no longer means hand-coding the lower-level cruft. Thus, you get a framework like Jack , which is similar to Python's WSGI and Ruby's Rack . Jack's based on the idea of fine-grained "middleware" libraries, able to be composed and reused, and there's a separate project, Nitro , to build such components for Jack. So Nitro builds on Jack, and Jack builds on CommonJS. This is an example of the ecosystem beginning to emerge in server-side Javascript. Use the Force! Building on Javascript's Strengths In the previous section, I treated Javascript as just another language with all the usual server-side abstractions and the well-trodden path towards modularity and reuse. That's not a bad thing at all, since we also benefit from the synergies of running the same language in the browser and the server mentioned earlier. Where things get really interesting, though, is with frameworks that exploit Javascript's unique characteristics. It's easy to get carried away with Javascript's efficacy as a regular scripting language, so let's remind ourselves that its roots are inside the browser. What the browser has, that a generic web framework doesn't, is the Document Object Model (DOM). This is the browser's model of the web page's contents. What if we gave Javascript access to a DOM? DOM access is a key feature of the Jaxer environment. It gives scripts access to an entire server-side Firefox instance. Developers can therefore manipulate content as they would in a client-side application, and output the resulting page. This overcomes one of the objections with Ajax apps, which is "what if the user has turned off Javascript?". The page still comes out as plain old HTML. That's a lot of power, and the patterns for using this kind of thing are not yet fully understood, but it has plenty of potential for exploration. There are also potentially great benefits for testing client-side applications if you can simulate an entire browser instance. jQuery founder has been working on a product called env.js . Where Jaxer is essentially an entire Firefox instance, env.js is an attempt to build a simulation of the browser environment from scratch, under active development. It's too early to say if its scope will stretch beyond testing and into the realm of server-side Javascript. DOM manipulation may be one characteristic thing about Javascript we can exploit, but there is also another (related) thing: event-handling. The language was more or less designed to respond to user events, so it has a great model for handling them that is familiar to any Javascript programmer worth their salt. For most server-side programmers, event-handling capability will yield a big fat "who gives a damn?". Server-side scripts don't sit around waiting for events to come in. They usually just look at an incoming request, deal with it, and send out a response. Then they exit as soon as they can. All good stuff, but there's a completely different paradigm possible. It's part of the trend towards the real-time web and the design pattern known as Comet. With Comet, the server holds on to the connection for a while, and continues to stream out information intermittently to the browser. The typical example is a two-way chat - as soon as one guy says something, the Comet server sends the message to the other guy. This is event-driven programming all over again, and compared to the usual suspects on the server, Javascript is well-placed to support this paradigm. A framework that's taking advantage of all this is node.js , or just "Node" to its friends. Node is interesting because it requires scripts to explicitly close the connection; if they don't close it, the connection just stays open and the script can handle events as they come in, usually by sending more information down to the browser. Less than a year old, the project already has a strong community and numerous derivative frameworks and applications . A similar model has been used in other frameworks, like Python's twisted, but Javascript may turn out to offer a neater syntax for this kind of thing. By daring to be different and using javascript for what it's best at, Node is shaping up as a framework to watch. The speed of Node apps is likely to give Javascript serious cred among server-side developers. Next page: The Cloud. Of Course, the Cloud! The Cloud. Of Course, the Cloud! No article on server trends could ignore the famous cloud. How does javascript work in virtualised computing environments? With a suitable engine, you can certainly set up an environment manually using amazon EC2, google app engine, or similar cloud hosts. However, you can do it easier than that with some of the other solutions around. Joyent took a big bet on Javascript when it acquired Reasonably Smart earlier this year; the host now offers a dead-simple runway to host Javascript scaleably. Aptana, the company behind the Jaxer platform described above, does likewise. Something's Going on Here Before we get too excited about this trend, I should make one thing clear. Conspicuous by their absence are the real-world server-side Javascript apps. There don't appear to be many sites running Javascript in the server at this time. Probably the most popular site powered by Javascript is EtherPad , the real-time collaborative notepad from AppJet, the company acquired by Google last week. This is a cautionary example, because AppJet launched as a cloud-based server-side Javascript framework before dropping it to concentrate on Etherpad. Aptana has also announced they are pulling back on Jaxer due to difficulties monetising it. Maybe this is more of a statement about cloud hosting revenue models than server-side Javascript, but it's worth asking how other attempts to propagate server-side Javascript will fare. One of the critical success factors will be a comprehensive standard API; it's a prerequisite to a vibrant ecosystem of interoperable components, and with a range of engines to run on. We now have the seeds of that with commonJS. Another factor is best practices for using the language; again, we've already discovered much of that as a side benefit of the Ajax revolution. Frameworks like Node, which build on Javascript's unique characteristics, are building on those to establish best practices for server-side Javascript. Reuse of both knowledge and practices will give Javascript its best chance yet to stand up as a viable alternative to the usual server-side suspects. Although Javascript is a far better language than was previously assumed, its syntax still has plenty of quirks. If we restrict ourselves to the subset of Javascript found in all the major browsers today - and arguably it makes sense to do so - it's arguably lacking certain features of other server-side languages. Those other languages are free to evolve autonomously; in contrast, Javascript's fate is heavily determined by standards bodies, browser manufacturers, and the patterns around how users upgrade their browser. In this sense, the language's strength - shipping with every browser - is also an Achilles' Heel. That said, the language may well prove "good enough". The benefits of "one language all the way down" may outweigh the cost in many cases. The will is stronger than ever to make server-side Javascript a reality, and it's translating into a visible surge of activity in the web community. There's the promise of code reuse and the possibility of cutting in half the number of programming languages involved in building a typical web application. Many smart developers have gravitated towards Javascript in recent years, as a means of producing world-class front-end apps. The attention has progressed our understanding of the language. Should server-side Javascript go mainstream, a third wave of Javascript developers will be joining the community and enriching the ecosystem. Photo by Dmitry Baranovskiy Discuss

Originally posted here:
Server-Side Javascript: Back With a Vengeance