We made the code base 80% lighter, the application requirements 80% lighter, the system requirements 80% lighter but we kept the majority of the functionality.. In fact, we introduced more via an API. More potential for developers.. We also made it wayyyy easier for developers to get started as we reduced the whole 3 language stack(scala, java, javascript) down to just one language.

So why Lite and why not V2?
We didn’t want to upset any foundation members. We knew we had a bunch of talented Java guys we didn’t want to upset and lose so we took the 1/2 cocked descision and tried to keep everyone happy. In hindsight, this was a terrible mistake. We are now 100% sure that the pure JS approach is the future, adoptions are up, performance is up, all of the indicators the foundation committed to from day one are showing positive signs.

We’re a family focused on making the collaborative web better. A group of people made this call and the same group of people are committed to finding a good solution.

Like any organization or individual we know that we have to correct our mistake so we’re on the hunt for a better name for Etherpad Lite.

A consideration is “LinePad” which would stand for Lite Is Not Ether.. Pad…
Another consideration is NodePad, also Etherpad V2, also Etherpad N (N for Node), also Etherpad JS…

So many choices, how do we make the right one?

We adopted Etherpad in December 2009 and instantly we knew we had a problem. The stack of software required to deploy Etherpad was huge and this meant deploying Etherpad was limited to Linux only. Our goal is to make collaborative editing the standard on the web and we knew that with the existing pre-requesitives we would be scaring too many people off. The pre-requisites also placed additional load on the server and increased complexity which meant that future development came at a really high cost. With this in mind we always knew we wanted to rewrite Etherpad to run on multiple OS’ and be kinder on system resources.

Etherpad Lite was the solution. Etherpad Lite does not suffer from the same flaws/gifts as Etherpad. The assumption people make (this is our mistake) is that some functionality does not exist in Etherpad Lite. Some of the pro functionality was replaced with an API so that sysadmins can write their own back-end and easily integrate Etherpad Lite into their current system. Writing a management back-end is a grind and not really core to what we wanted to achieve but we will soon be releasing something that will “tick this box”.

In general we would recommend you use Etherpad Lite however there is a certain scenario you may choose to use Etherpad.

Etherpad (NON LITE) should be used if you want a really quick, short term fix for a problem that requires managing multiple users with permissions. We would recommend a maximum of 15 concurrent users and be mindful that support may be limited because most of the community is now working on Etherpad Lite. We would still recommending using Etherpad Lite and doing a days worth of development integrating your existing CMS using one of our many libraries.

Etherpad Lite should be used the rest of the time. If some functionality is missing please contact us and/or look on the web. We have a service and consultancy team waiting to help and we want to help you get Etherpad integrated into your organization/platform/service.

What’s the future of Etherpad Lite?

We have set milestones up to V1.3 which will take us into 2013 and we’re constantly organizing meet-ups and hackathons. We are not excluding any features or ideas and given time and resources we will achieve our goal. We want to build a community that is passionate about building Etherpad and continuing the development so to do this we have issued a number of gun.IOs and other financial incentives that have complimented our employment program.

What’s the future for Etherpad (Legacy)

We’re obviously not completely stopping our support for Etherpad Legacy but we are doing everything we can to encourage developers and users to adopt Etherpad Lite. Given time we hope to either rename Etherpad Lite to Etherpad or Etherpad v2 or something, we have quite a few decisions to make here and we hope to make them over the next few months.

Example:

EPLiteClient api = new EPLiteClient(“http://etherpad.mysite.com”, “FJ7jksalksdfj83jsdflkj”);
HashMap pad = api.getText(“my_pad”);
String pad = pad.get(“text”).toString();

Welcome to 2012 everyone, it’s going to be a Heck of a year for the Etherpad foundation so stay tuned in for a plethora of exciting announcements!

Enjoy!

If you’re interested in joining, tuning in remotely, or starting your own meet-up site, please add your details to this pad!

• It implements the Etherpad Lite API, more infomation on the API can be found on the Etherpad Lite wiki.
• It matches the API in structure as closely as it can.
• It parses the returned JSON into strongly typed objects to allow the use of intellisense and reduce the use of magic strings.
• The library is written in C# and uses .Net Framework 4.

More details and download here