tag:blogger.com,1999:blog-222477822011-04-21T22:13:15.927+01:00Cake Muncherhttp://www.blogger.com/profile/17671041238199427192noreply@blogger.comBlogger31100tag:blogger.com,1999:blog-22247782.post-1140189253396936752006-02-17T15:12:00.000Z2006-02-17T15:14:13.413Z<a onblur="try {parent.deselectBloggerImageGracefully();} catch(e) {}" href="http://photos1.blogger.com/blogger/7219/2261/1600/cake_on_rails.jpg"><img style="margin: 0pt 10px 10px 0pt; float: left; cursor: pointer;" src="http://photos1.blogger.com/blogger/7219/2261/320/cake_on_rails.jpg" alt="" border="0" /></a><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/22247782-114018925339693675?l=cakeonrails.blogspot.com' alt='' /></div>Cake Muncherhttp://www.blogger.com/profile/17671041238199427192noreply@blogger.com0tag:blogger.com,1999:blog-22247782.post-1139606154533180512006-02-10T21:09:00.000Z2006-02-10T21:16:30.710ZSo Cake 2.0 has been underway for less than 24 hours, a few concerns in the rising Cake community must be addressed if we are to meet our aims of VC investment and eventual acquisition by mid February 2006.<br /><br /><span style="font-weight: bold;">Cake 2.0 URLs</span><br />We feel there are mixed feelings amongst the Cake 2.0 community about the state of cakeonrails URL's. To quote an example from one member; "I want my cake faster, I don't want to type html in every time I feel like a Cake 2.0 mashup".<br /><br />In this instance we feel the user is right, but we have come so far already? Can we really justify changing all of our URL's at this stage to more Cake 2.0 friendly versions? A topic I am sure we will cover much more in the future.<br /><br /><span style="font-weight: bold;">Cake 2.0 Costs</span><br />With the escalating costs of making Cake, should we consider a pay per content appoach? Certainly the API is proving popular and there is a potential means for making profit there, but as discussed at the Web Apps conference there is currently no standard for billing through an API. As a showcase of Web 2.0 (and indeed Cake 2.0) technology we feel we should wait for this standard to emerge.<br /><br /><span style="font-weight: bold;">Cake 2.0 Pirates</span><br />It has come to our attention that some people are taking advantage of the uncompiled nature of Cake's HTML source code. They are partaking in an unprecedented escalation of Cake 2.0 abuse. We think maybe a more secure method of distributing Cake 2.0 is needed, but it must be done without going against the open standards encouraged by Web 2.0.<br /><br /><br />We must face these challenges head on if we are to succeed in providing the next generation of Cake for the future of the web. It is now clear that Cake 2.0 is the way forward and we will look forward to the challenges and hurdles that lie ahead<div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/22247782-113960615453318051?l=cakeonrails.blogspot.com' alt='' /></div>Cake Muncherhttp://www.blogger.com/profile/17671041238199427192noreply@blogger.com2tag:blogger.com,1999:blog-22247782.post-1139578174762809172006-02-10T13:26:00.000Z2006-02-10T13:29:34.770ZInspired by the 'Future of Web Apps' conference this week we decided to start our own Web2.0 site.<br /><br />So here it is... <a href="http://www.cakeonrails.co.uk/">http://www.cakeonrails.co.uk/</a><div class="blogger-post-footer"><img width='1' height='1' src='https://blogger.googleusercontent.com/tracker/22247782-113957817476280917?l=cakeonrails.blogspot.com' alt='' /></div>Cake Muncherhttp://www.blogger.com/profile/17671041238199427192noreply@blogger.com2