Skip to main content

Google lights a Campfire...

This week Google launched their App Engine Platform to add their hand to the collection of products and services provided by large and small providers of web frameworks. As a developer of just such a framework still in steath, the announcement is not a surprise (if it is to any of the other guys they may have a few things more to worry about) but with this announcement Google also announced a few "proof of concept" applications built using their App Engine. To demonstrate the ability to build apps quickly, three of their developers are said to have worked on their "spare time" to create a free web group chat application called HuddleChat very much like the service provided by 37Signals Campfire product. I am quite familiar with Campfire as in my initial research for developing a collaboration API in my framework 2 years ago I came across their website. The product serves a simple purpose of allowing a team of individuals to come together and converse in a chat room while sharing files collaboratively. It is precisely this simplicity that has made the product vulnerable, the technology needed to create such an app makes it simple to reproduce with other technologies. There is very little in the way of innovative distinction in the Campfire product that can prevent others from copying the functionality. Also, as far as I know the product implementation may not have any patents behind its technology. True enough, Google's Huddle chat is inspring some controversy in the blogosphere for how closely it mirrors both the look of Campfire and its functionality.

Having designed a collaboration tool that encompasses all the functionality provided by Campfire and Huddle Chat but includes a patent pending set of technologies critical to the scalability of the implementation I wonder why 37signals felt entitled to complain. It is clear from looking at the interfaces that they are layed out similarly but I wouldnt call one a clone of the other, Google could have used a different layout (say like parachat, meebo or userplanes for example) but the main fact that they are all using the same simple implementation method to make the chat work is common regardless of the interface. The machine behind is what needs to be unique and protected. If it is novel and efficient, it will allow a company to compete with established players and gain traction without fear of strong competition for a period of time that will allow them to hopefully thrive. This is what I hope to do with my product which will soon be coming out of stealth. I look forward to seeing if Google can "throw together" a scalable competitor to my service when I do...just so long as it takes them about a year or two to get it out there;).

Bring on the competition I say!


Popular posts from this blog

Highly targeted Cpg vaccine immunotherapy for a range of cancer


This will surely go down as a seminal advance in cancer therapy. It reads like magic:

So this new approach looks for the specific proteins that are associated with a given tumors resistance to attack by the body's T cells, it then adjusts those T cells to be hyper sensitive to the specific oncogenic proteins targeted. These cells become essentially The Terminator​ T cells in the specific tumor AND have the multiplied effect of traveling along the immune pathway of spreading that the cancer many have metastasized. This is huge squared because it means you can essentially use targeting one tumor to identify and eliminate distal tumors that you many not even realize exist.

This allows the therapy for treating cancer to, for the first time; end the "wack a mole" problem that has frustrated traditional shot gun methods of treatment involving radiation and chemotherapy ...which by their nature unfortunately damage parts of the body that are not cancer laden but …

Engineers versus Programmers

I have found as more non formally trained people enter the coding space, the quality of code that results varies in an interesting way.

The formalities of learning to code in a structured course at University involve often strong focus on "correctness" and efficiency in the form of big O representations for the algorithms created.

Much less focus tends to be placed on what I'll call practical programming, which is the type of code that engineers (note I didn't use "programmers" on purpose) must learn to write.

Programmers are what Universities create, students that can take a defined development environment and within in write an algorithm for computing some sequence or traversing a tree or encoding and decoding a string. Efficiency and invariant rules are guiding development missions. Execution time for creating the solution is often a week or more depending on the professor and their style of teaching code and giving out problems. This type of coding is devo…

AgilEntity Architecture: Action Oriented Workflow

Permissions, fine grained versus management headache
The usual method for determining which users can perform a given function on a given object in a managed system, employs providing those Users with specific access rights via the use of permissions. Often these permissions are also able to be granted to collections called Groups, to which Users are added. The combination of Permissions and Groups provides the ability to provide as atomic a dissemination of rights across the User space as possible. However, this granularity comes at the price of reduced efficiency for managing the created permissions and more importantly the Groups that collect Users designated to perform sets of actions. Essentially the Groups serve as access control lists in many systems, which for the variable and often changing environment of business applications means a need to constantly update the ACL’s (groups) in order to add or remove individuals based on their ability to perform certain actions. Also, the…