Angel Blog Reviews » open-source

Open Source: Facebook Is Now an Apache Software Foundation Gold Sponsor

admin — Tue, 12 Jan 2010 18:42:43 +0000

Facebook just announced that it has become a Gold sponsor of the Apache Software Foundation. According to Facebook's David Recordon, the company wants to give back to the open source community that allowed Facebook to develop and contribute to projects like the Thrift framework, Hive , memcached and Cassandra . Apache Gold members donate $40,000 per year to the project. It's worth noting that this is not Apache's highest sponsorship level. Google, Yahoo and Microsoft are platinum sponsors and give $100,000 per year. Sponsor In total, Facebook has developed or contributes to over 20 open source projects . Facebook also released the real-time web framework Tornado , one of FriendFeed 's core technologies, as an open source project shortly after it acquired FriendFeed in August 2009. As Recordon notes in today's announcement, technologies like Hive and Cassandra that were first developed in-house by Facebook are now being used and sponsored by a diverse group of companies ranging from CBS and Rackspace to Digg, last.fm and Twitter. There can be little doubt, however, that open source is, as Apache Foundation chairman Jim Jagielski puts it, "in Facebook's DNA." We can't help but wonder, though, why Facebook didn't decide to go all the way and buy the Platinum sponsorship package . Become a Friend of ReadWriteWeb on Facebook . Discuss

Visit link:
Open Source: Facebook Is Now an Apache Software Foundation Gold Sponsor

Google Brings Friend Connect, Social Features to Drupal & Joomla

admin — Tue, 12 Jan 2010 05:15:39 +0000

Google has just announced that its powerfully social Friend Connect features are now available for open-source content management systems Drupal and Joomla . Google Friend Connect (GFC) allows sites with these CMSes to integrate many social features without having to write any code. The impact of the integration has the potential to be significant, as Drupal in particular is one of the most widely-used content management systems in use on the Web today, powering sites from WhiteHouse.gov and NASA.gov to TheOnion.com and websites for celebrities and musicians like Britney Spears and Eric Clapton. Joomla is used by such institutions as Harvard, MTV and Citibank. Sponsor Friend Connect essentially allows site visitors to become site members by using profile information from services such as Google, Yahoo!, Twitter and more. With user accounts authenticated via OpenID, site administrators can add Friend Connect's social bar, a site members gadget, the Friend Connect comments gadget or recommendations in any part of the site they choose. In addition to adding social gadgets, Friend Connect also allows site admins to conduct polls, monitor community growth, create and distribute email newsletters, run ads through AdSense, export user data for a site's entire community (as XML or JSON) or create their own apps using the GFC APIs . "Even site owners without programming experience can add these plugins," writes developer and open-source aficionado Mauro González in Google's Social Web blog post. "Now that Friend Connect is integrated with these popular open source CMS platforms, site owners can make registration easier for users and offer them a set of social features - all without writing a single line of code." GFC represents an interesting - and perhaps underused - suite of tools in an increasingly competitive space. Many site owners are adding social features to blogs and sites through systems such as JS-Kit's Echo or Disqus , and Joomla and Drupal both have many extensions and plugins to allow for the same kinds of features and functions. Still, making GFC available for the CMSes that power many highly visible sites around the Web might do a lot of good for that product. Overall, we see this announcement as indicative of a set of trends: Portable user identities, highly interactive content, portable communities and open-source software. What do you think: Will more site users be integrating Friend Connect to allow for more social website experiences? Let us know your opinions in the comments. Discuss

Read the rest here:
Google Brings Friend Connect, Social Features to Drupal & Joomla

How the Cathedral and the Bazaar Is Shaping the Future of Comics

admin — Sun, 10 Jan 2010 01:22:00 +0000

Today's startups, entrepreneurs and investors live and die by what seem like a series of holy proverbs. "Release early, release often" is perhaps one of the most poignant phrases when considering product launch and feature scope. On this cold Saturday, we're paying homage to the origins of the concept by recognizing one of the seminal works in programming philosophy, and looking at a recent startup that's taken it to heart. Sponsor In the late nineties Eric S. Raymond presented The Cathedral and the Bazaar convincing Netscape to publish open source code. The work's premises "given enough eyeballs, all bugs are shallow" and "release early, release often" were meant to justify early releases and crowdsourcing community feedback. While his work originally made a case for open source releases, it has gone on to inspire many outside of the open source realm. Lead by Micah Baldwin, TechStars' comic platform Graphic.ly is launching its beta version under the "release early, release often" tenet. Said Baldwin in a recent blog post , "If we are truly going to get the community involved, we need them involved early and often. We need them now." ReadWriteWeb first covered the mobile comic platform in November under its original name, TakeComics . Since then the company has rebranded as Graphic.ly, announced raising a little over a million dollars from Starz Media and appointed Baldwin as CEO. As a serial entrepreneur, Baldwin rationalizes his company's early release saying, "So many young entrepreneurs get stuck in the 'What if' world and try to release the perfect app. At Graphic.ly, we just released our Baby Beta, which frankly sucked. Badly. But we are getting amazing feedback, and its clear that it will be such a better product in the long term." Baldwin is using a combination of GetSatisfaction and Zendesk to manage early-stage feedback. Graphic.ly is also looking to adapt products like Google Moderator for proactive feedback in order to engage community members in the engineering and product discussions. When asked about possible outcomes for the release, Baldwin replied, "The worst case scenario is that we don't engage our community properly and lose their trust. There is nothing more dire than lost trust. The best case is that everyone who uses Graphic.ly sees their fingerprints all over it and shows it to their friends proudly, saying 'I built that. That's something I did.'" The service's first batch of invites got out tonight, to register for the service fill out the form here . Discuss

Read the original post:
How the Cathedral and the Bazaar Is Shaping the Future of Comics

I Run 13 Browsers At Once; 11 of Them Just Went Open Source

admin — Thu, 07 Jan 2010 21:06:01 +0000

FluidApp is what's called a Single Site Browser and is a great way to pull key websites you use throughout the day out of your primary browser and onto your Mac dashboard as standalone applications. It's super easy for anyone to use. The service has a thriving community of users - I have 10 Fluid browsers running on my computer right now and wouldn't want to work without them. In fact, I'm writing this blog post from Movable Type inside a Fluid Browser. In a quiet mid-December move, FluidApp developer Todd Ditchendorf put "most of the code behind Fluid" up on Github under an open source license. That's very good news - new developments are already coming fast and furious. If you haven't checked out Fluid before, now is a great time. Sponsor There's something magical about the way single site browsers let you use different web apps. They don't get lost in tabs. They don't fall prey to browser crashes. You can put a handsome icon in your doc to jump over to them. Windows users looking for a similar experience should check out Bubbles or Mozilla's Prism . Now that Fluid for the Mac is open source though, it will be very exciting to see what features are added next. Creator Ditchendorf says he has some more exciting plans under his hat but nothing to show off yet. Watch this space. What's your favorite Fluid App? One of my favorites is LazyFeed . Next: 15 Fluid Apps You Can Build For Your Business . Discuss

View post:
I Run 13 Browsers At Once; 11 of Them Just Went Open Source

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

5 Cool Things to Know About Google Chrome Extensions

admin — Wed, 09 Dec 2009 04:43:11 +0000

The Google Chrome team released a beta version of its Mac browser this morning and opened up an official gallery of browser extensions . That's exciting news because the addition of more than 300 extensions, combined with blazing speed and good stability, makes Chrome the best browser on the market today. We got a chance to talk with Nick Baum, Product Manager and Brian Rakowski, Director of Product Management at Google Chrome this afternoon and they shared a number of interesting tidbits with us about the nature and future of extensions in Chrome. Sponsor Chrome was released more than a year ago and users have been clamoring for extensions ever since. Rakowski and Baum said that a request for extensions was bug #18 filed in the browser's bug tracking system - it's something that Firefox has conditioned users to expect. Now those extensions are here and it's a very interesting story. Understanding the Versions of Chrome Between Chrome, Chromium, dev and beta releases, things are getting a little complicated. Here's how it breaks down: Chromium is open source developer channel, "the bleeding edge" of Chrome development. That's what we've been using here on Mac and it's the only Mac version today that supports extensions. It's untested and less stable than the other versions. We've been using it for months, though, with only occasional problems. Chrome is the official release. There are 3 versions of Chrome: dev , beta ( Windows or Mac ) and stable (Windows only). The vast majority of users use the stable version, Mac users got beta build 4.0 today. Dev builds come out every week or so and are at most 1 week behind Chromium. Baum and Rakowski asked in our interview for us to please switch to using the Dev version for Mac instead of Chromium as soon as it supports extensions. Mac Dev Version Will Get Extension Support Very Soon Some of Nick Baum's Favorite Chrome Extensions So Far Aviary - screen capture and image editing Google Docs PDF/PPT Viewer Google Translate - truly, a wonder to behold Brizzly - an advanced Twitter experience, built by Baum's former co-worker on Google Reader, Jason Shellen Right now the official extension gallery won't allow Mac users to download extensions. Officially, at least. This bookmarklet will allow you to install them in Chromium on a Mac with just one extra click. (Thanks, MG Seigler , for finding that.) That bookmarklet will not allow you to use extensions in the official beta for Mac that launched today, just in Chromium. Baum and Rakowski told us today that the next dev build for Mac will allow extensions. That could be out as early as tomorrow morning or in a few days, and it's anyone's guess when extension support will come to the Beta version released today. (Who wants to use the Beta version when Dev is so much cooler?) Anyone can get extensions from an unofficial site called ChromeExtensions.org and if you're on a Mac it's probably most effective tonight to grab Chromium and the bookmarklet above. Then you can get extensions from the official site as well. Chrome Extensions Are Not Like Firefox Extensions Unlike Firefox extensions, Chrome extensions install without a browser restart and they update automatically. Too many extensions have been a part of the bloat that's made Firefox-use nearly intolerable for many of us, but the Chrome team says extensions will cause no more drag on Chrome performance than opening up a new web page in another tab would. That's a big part of the premise of Chrome, that every process is running distinct from other processes, so one tab can't slow or crash the others. It's an architecture well suited to running web applications, not just loading web pages, and it's great to hear that the extensions platform works the same way. GreaseMonkey? Oh, There Will Be GreaseMonkey One of the most enjoyable tide pools of innovation in the Firefox extension world is built on top of the Javascript user script plug-in GreaseMonkey . These tiny scripts re-organize web pages in radical ways for more usefulness and fun. Scripts like AutoPagerize will load the next page at the bottom of the one you're on, creating a continuous scroll, or WikiDashboard will insert a drop-down dashboard into every Wikipedia page to show a scatter plot graph of who has edited that page the most. The fun never stops with GreaseMonkey. What of Chrome, though? Guess where, Aaron Boodman , the creator of GreaseMonkey works now? That's right, on the Chrome Extensions team. Boodman recently made it even easier for GreaseMonkey scripts to be added to Chrome than they are in Firefox. A single click transforms the scripts into Chrome Extensions, at least for Windows users. We haven't found a successful Mac implementation yet, but we've got our fingers crossed that this will no longer be an issue when full extension support comes to Chrome for Mac. Red Hot APIs On the Way Baum told us today that the team "will add APIs for other data types soon, personal web history being a prime candidate, so extensions will be able to access that and manipulate it in all sorts of ways." That sounds great. It's one thing for a browser to promise not to sell my web history, but it's a whole new ball game when developers can build software that lets me derive all the more value from the history of my activity around the web. Bring it on, Team Chrome! We might feel a little guilty for abandoning the wonderful community project that is Firefox, but this new browser is just so damn good it's hard not to give it a serious try. It just so turns out, we have a particularly relevant sponsor this month that we should point to. Add-on-Con is a major event all about browser add-ons. It's being held in Mountain View, CA this Friday. Google is a sponsor and Aaron Boodman, the man behind GreaseMonkey and now working on Chrome Extensions, is a speaker. Check it out! Discuss

Top 10 Internet of Things Products of 2009

admin — Tue, 08 Dec 2009 18:17:00 +0000

2009 has been a turning point for the Internet of Things , when real world objects (such as lights, cars and packages) get connected to the Internet. This trend has added a significant amount of new data to the Web, so for that reason alone it is an important development. Having said that, many of the following top 10 list are not yet mainstream products. But we expect some of them to become well known over the coming years. Underlying the Internet of Things are technologies such as RFID (radio frequency identification), sensors

Offline Gmail Becomes Standard Feature (But Still Uses Gears?)

cgseo — Tue, 08 Dec 2009 14:08:34 +0000

This morning Google announced that "offline Gmail" is leaving the Gmail Labs testing area and will be implemented as a standard feature for all users. Once enabled, this feature allows you to access your Gmail even when no internet connection is available. You can read and respond to messages, star them or label them just as you would if you were online. When a connection is restored, all the changes you made are synced with Google's servers and any messages in your Outbox are sent out. As of today, all Gmail users will now have this feature turned on by default, however those who have never used it before will need to configure it first in order to take advantage of the enhanced functionality. Sponsor Gears Makes a Public Debut The Labs section of Gmail is where experimental and in-development programs, add-ons, and extra features are housed, allowing Gmail users to switch them on or off as desired. Offline Gmail was one of those experiments, launched back in January of this year. Using Gears , an open source plug-in technology designed by Google, email messages are downloaded to your local machine when you switch to offline mode. Also, if your internet connection is dropped unexpectedly, offline Gmail is automatically enabled. In the year in which offline Gmail has been in testing, the company says they received a lot of feedback from users. Some of the requested features have already been implemented, including the ability to choose which messages get downloaded for offline use and the ability to send attachments while offline . According to the Google blog post , anyone who was already running the Labs version of offline Gmail won't have to make any changes but those who had never turned on the setting will need to do the following: Click the "Settings" link in the top-right corner of Gmail. Click the "Offline" tab. Select "Enable Offline Mail for this computer." Click "Save Changes" and follow the directions from there. But Isn't Google Switching to HTML5? At first it seems like "graduating" offline Gmail from Labs is step in preparation for next year's launch of Google Chrome OS , the web-based operating system that ditches the desktop, the hard drive, and computer applications for a web browser where everything users access lives online. Because online applications require an internet connection to work, there have been some concerns as to how functional this OS will be in a world that is not yet blanketed in Wi-Fi or 3G. Since Google has made no mention of built-in hardware providing 3G and cellular access as a backup to Wi-Fi, there will be a lot of programs that simply don't work when you go offline...that is, except for the programs that Google develops itself. The company has already implemented its Gears plug-in on two other products in addition to Gmail: Google Reader and Google Docs . Meanwhile, other companies have also adopted the technology including online office suite Zoho and to-do list app Remember the Milk . What's odd about this launch of Google Gears into primetime via Gmail is that this seems to conflict a bit with what Google execs announced last month regarding the company's plans for its upcoming operating system, Chrome OS. During the Q&A session at the end of the press event , an audience member asked about Google Gears support to which Google's VP of Product Management Sundar Pichai replied by saying that Chrome OS will take advantage of HTML5 for local storage. He made no mention of Gears. HTML5 , a proposed revision to HTML, the markup language of the World Wide Web, includes offline storage as one of its many new features. And it's this specification that Google's plans to support in the future, not Gears, according to numerous reports. For example, in a recent article in the L.A. Times , a Google spokesperson was quoted as saying: "We are excited that much of the technology in Gears, including offline support and geolocation APIs, are being incorporated into the HTML5 spec as an open standard supported across browsers, and see that as the logical next step for developers looking to include these features in their websites." Also, Linus Upson, the engineering director at Google told PC Magazine that the company was abandoning its work on Gears 2, the next version of the plug-in, and will be focused on HTML5 instead. "You can almost think of what's in HTML5, with app cache, and database, and those things, as essentially Gears [version] 2," he said. "That's how we view it." Upson noted, too, that the company would be able to influence the adoption of HTML5 through their web browser, Google Chrome, the foundation of the new Chrome OS. "Now that we're a browser vendor, we can help move HTML5 forward not as a plug-in, but as part of Chrome," Upson said. So in other words, the Gears functionality being switched on now in Gmail may not be the same technology used a year from now when Google Chrome OS hits the market. That begs the question: why bother? If Google plans to replace Gears with HTML5 in the near future what's the point of rolling out the soon-to-be abandoned plug-in to all its users now? Will Gears and HTML5 converge somehow or will Google just rip out the plug-in in favor of HTML5's "plug-in-less" technology instead? Let us know what you think in the comments. Discuss

See more here:
Offline Gmail Becomes Standard Feature (But Still Uses Gears?)

Where do Short URLs Go When They Die?

admin — Tue, 01 Dec 2009 22:00:00 +0000

In late October, after Bit.ly had firmly established itself as Twitter's service of choice, it looked like URL shortener service Cligs would close down. As of today, the company will see a new management team as social bookmarking service Mister Wong has agreed to acquire it for an undisclosed sum. Sponsor Says Clig's founder Pierre Far, "I'm very happy with Mister Wong as they have an excellent track record of building large communities and keeping them happy. They also have the resources to continue the development of the service and keep it competitive in the market. Cligs has always been a side project, but the service grew too big to take care of in my spare time." Far began his quest for a buyer in early October. In August ReadWriteWeb covered the commercial demise of URL shortener service Tr.im and its subsequent resurrection as an open source release . A number of services have failed to find exit strategies in this crowded space so it appears that Far's deal with Mister Wong is fortunate one. When we asked Far where short links go when they die, he pointed to 301works.org . 301works is an Internet Archives initiative created to preserve short URL links in the event of a shutdown. If a short URL company faces closure 301works takes control of shortening domain services and ensures that links remain intact. While the technical side of the program has not been completely laid out, a number of companies have agreed to show the 301works seal including Bit.ly, Cligs, Twurl , Awe.sm and AppsFire . To apply check out 301works.org here . Discuss

More here:
Where do Short URLs Go When They Die?

Dell Releases Customized Version of Chrome OS

admin — Fri, 27 Nov 2009 13:48:36 +0000

Dell has just released a customized version of Chromium OS, the open source code behind Google's new operating system called Chrome, in a build designed specifically for Dell Mini computers. According to a blog post on the Dell Community site , several company employees were inspired create this custom version after seeing Engadget's video showing Chrome OS running on a Vostro A860 netbook. After tinkering around with the code, they were able to create their own version of Chromium OS, complete with functional Wi-Fi drivers, and have made the build available for download as a USB key image file from the Direct2Dell blog . Sponsor About Google Chrome After last week's sneak peek at Google's upcoming operating system dubbed Google Chrome OS, tech enthusiasts everywhere have been playing with the open source code which Google released to the community on the day of the press conference. This code, called Chromium OS, lets anyone take the basic building blocks of Google's operating system and customize it for their own purposes. Going the open source route isn't just an example of Google's desire to "not be evil," but protects the company from anti-trust, anti-competitive claims surrounding the new project - a project which is basically an OS that runs only one web browser: Google Chrome . In fact, Google's browser is the operating system in its entirety. No desktop applications will be supported on this web-based, Wi-Fi only machine. As Google's VP of Product Management, Sundar Pichai, said during the press event, if any other browser maker wants to build their own version of the OS using their own browser, they can. Since the launch of the Chromium OS source code, there have been a number of articles explaining how to run the operating system in a virtual machine on your own computer as well as how to boot the operating system from a USB flash drive . But up until now, these efforts have been steered by enthusiastic technology users and not those associated with any large computer manufacturer such as Dell. And while the Dell Chromium build isn't exactly an "official" company product, it's noteworthy for the fact that it was designed by company employees, posted publicly on a Dell website, and is customized to run specifically on Dell Mini computers. Dell's Chromium OS Build According to the Dell blog post , the USB key image file (available here: http://linux.dell.com/files/cto ) only works on Dell Mini 10v computers . Most importantly, the build makes the built-in Broadcom Wi-Fi adapter on these machines functional, a feature needed when running a web-based OS. After all, what good is a cloud operating system if you have to be tethered to an ethernet cable? The blog post includes instructions on how to copy the USB image file to a USB flash drive, but unfortunately the directions are aimed only at those who have access to another Linux machine. We're not sure why Windows and Mac users couldn't just modify the instructions found on this website to make their own Dell Chromium OS USB keys by substituting the Dell build for the one hosted on that site. In addition, if you're interested in trying out the Dell version of Chromium OS, there are a couple of things you should know: You'll need a hefty USB key drive - 8 GB minimum. It may take 5-10 minutes for the Chromium OS network connection manager to "see" the Wi-Fi access points. Some issues with the connection manager are still present. If it gets hung, reboot and try again. And by the way, there's no "reboot" - you have to press the power button on the Mini laptop. The Dell build is unsupported and minimally tested - use at your own risk. If you're still feeling brave, the download is available here . Discuss

Continued here:
Dell Releases Customized Version of Chrome OS