Lushable update April 2008: A Facebook a Google and an expensive Pizza

May 9th, 2008

So here is the April update of the Technology world seen though the eyes of Lushable editors. The first story we wrote about was the much talked about sale of domain name pizza.com which was sold bfor $2.6million. We wrote about the now launched Facebook chat whilst it was in the pre-launch phase. I have to say, the Facebook chat system is superb, one of the best additions to social networking website Facebook.com. I think its great that you can see all your Facebook friends online and chat to them when there online, I am now visiting Facebook more, sometimes just to see who is online and available to chat if I’m bored online. Jose wrote a more in depth review about the service in the post titled Facebook chat hands-on. Jose also wrote about the launch of Google’s app engine and a more in depth look into the Google app engine.

Now in May and now neerly 6 whole months since Lushable Technology and web 2.0 start up news launched we have retreated to our old look, the old theme for the blog, we’re still planning to launch more versions of the site and hire more editors.

Hire a Blogger from just $1.85 per post

May 8th, 2008

Techreform offers a range of blog writing and content writing services tailored specifically for webmasters, web publishers, bloggers, affiliate marketers and small business. Based in the United Kingdom we service customers the world over including United States, Canada and Europe.

Read the rest of this entry »

Google App Engine under minor turbulences

April 9th, 2008

ReadWriteWeb´s Josh Catone posted about HuddleChat, the App used by Google to Demo their App Engine, and found a strikingly resemblance with 37Signals Campfire and discovered some good tidbits from that resemblance because 37 Signals Jason Fried stated:

“We’re flattered Google thinks Campfire is a great product, we’re just disappointed that they stooped so low to basically copy it feature for feature, layout for layout,”

And he would be right just judging from the screenshot:

I mean, this is Google, ok, that is already shielded because the HudleChat app was developed apart from Google ties eve if done by Googlers. but it is pretty obvious it is a complete rip off. if this guys are from Google and where building this to Demo Google App Engine and were indeed producing a Copy of Campfire why the din´t:

  1. Changed the orientation of the layout?
  2. Change the measures of the design so it don´t looks the same?
  3. Change the look so it looked more separated from the source?

Those are 3 very simple things they could have done to avoid claims of rip off. but they didn´t. one would blame the Googlers that did this because after all Google denied connection to this. but then there is the background behind campfire as written by Josh Catone:

“Another interesting wrinkle to this story: 37Signals is supported by Amazon founder Jeff Bezos, who invested in the company in July 2006, and the Chicago-based company’s web apps all run on Amazon’s web services platform, a competitor in many respects to Google App Engine. Could it be that Google purposely chose to clone one of Amazon web services’ greatest success story specifically to show off the power for their new platform? Perhaps it wasn’t a coincidence that Google unveiled App Engine at an event it called Campfire …”

Then it don´t seems like a coincidence, does it?. the most incredible part is the pro google sentiments of own ReadWriteWeb commenters in that post where they blast against 37 signals and supporting Google.

Need to be read to be believed

Another rare moment in Google App Engine debut is that we have underestimated TechCrunch traffic power or there is something fishy on the supposed limits of the App Engine because Techcurnch very simple app went down too fast to be true. i just don´t buy this..

And it was true, the error message is used for any kind of outage because Google App Engine also showed the same error when it got down. so much for unlimited scalability indeed..

Google App Engine Launches

April 9th, 2008

Google App Engine is out and the premise is clear: Google against Amazon and Google getting ready to battle Microsoft when the latter decides to enter into the game.

The Google App Engine has been seen in the same way Blogger was when introduced previously to Google buyout: The Easiest Solution and for the masses.  the question is if it works as it should?

It does but there is doubt if it can really be used to host big projects. and if big projects will be using it since unlike Amazon web services. you choose a whole predefined package and not only the parts you only need like in Amazon web services where you chose from 3 parts, being able to use just one or all 3.

The Promises of Google are:

“Leveraging Google App Engine, developers can:

  • Write code once and deploy. Provisioning and configuring multiple machines for web serving and data storage can be expensive and time consuming. Google App Engine makes it easier to deploy web applications by dynamically providing computing resources as they are needed. Developers write the code, and Google App Engine takes care of the rest.
  • Absorb spikes in traffic. When a web app surges in popularity, the sudden increase in traffic can be overwhelming for applications of all sizes, from startups to large companies that find themselves rearchitecting their databases and entire systems several times a year. With automatic replication and load balancing, Google App Engine makes it easier to scale from one user to one million by taking advantage of Bigtable and other components of Google’s scalable infrastructure.
  • Easily integrate with other Google services. It’s unnecessary and inefficient for developers to write components like authentication and e-mail from scratch for each new application. Developers using Google App Engine can make use of built-in components and Google’s broader library of APIs that provide plug-and-play functionality for simple but important features. “

And the set of features is described as:

  • Dynamic webserving, with full support of common web technologies
  • Persistent storage (powered by Bigtable and GFS with queries, sorting, and transactions)
  • Automatic scaling and load balancing
  • Google APIs for authenticating users and sending email
  • Fully featured local development environment
  • But as with everything Google, where all is half truth and half reality, the initial limitations are severe and cannot give a exact projection on when we will see the full service running as it was envisionaed and much less if it will run in such a way.

    Via Google App Engine Blog and Techcrunch