I just got a tip from AppJet front-end developer, Aaron Iba, about plans for self-hosted AppJet instances. "We're thinking about releasing this soon." This was also just added to the FAQs page. What this means is that one could download the backend that runs the apps and install it locally, on servers, or even Amazon Web Services. Why would someone want to do this when everything is already hosted by default for free? The answer is that it allows an app to use more resources, namely storage space and processing time. An avenue for intensive apps, such as Agglodex, is desperately needed. Some people also get a kick out of DIY projects. The self hosting option appeals to experienced techies, whereas the recent beginner's programming tutorial was an outreach to fledgling or even non-techies. This suggests either a lack of targetted focus or a quest for ubiquitous dominance for the AppJet team.The prospect of achieving a serious foothold in the web framework space is intriguing. The prejudice against JavaScript might be just too much, in which case it will never gain traction. Although, AppJet is not the only company toting a JavaScript web framework. Aptana Jaxer has an interesting approach that blurs the line between client and server code even further. With over 2 million downloads, the market is clearly there.
To explore the degree of success the AppJet platform can achieve, we need to consider the business style of the team. We know they are Y Combinator funded, which historically seems to take a less bottom-line focus (although the latest round seemed much more commercial). Note that AppJet has been public for over three quarters with an apparent revenue stream of zero, with only polls about desired premium features. It would almost seem that they aren't interested in money at all! This is a very good sign for driving adoption, as long as they stay in business. (The one thing that worries me is the coddling of beginning programmers. This is good for PR, but wasting valuable time for the 3 employees. The point of a framework is to coddle the application structure. Syntax help and programming theory is a job for the community.)
Let's face it: web platforms have to be free and open. LAMP is the reigning king. Ruby on Rails and Django are the up-and-coming challengers. All three are open source and 100% free. Microsoft's ASP.NET--not so much. So to have any chance at all, AppJet needs to be open too. Luckily, the FAQs indicate that exact plan.
Or maybe not? Maybe AppJet is part of the new-wave sandbox hosting, such as Google's AppEngine, that doesn't directly compete against traditional web frameworks. It's analogous to Reddit vs. Slinkset. Do you want to DIY or get up and running right away? As time rolls on, it is clear that the level of abstraction increases. It is even getting to a point where dealing with virtual instances of computers on Amazon Web Services is too much work, if code can just run on one huge platform. The cowboy era is ending and the mesh is beginning.
And this is where AppJet comes in. If they have the business sense, they will host the runtime on AWS and charge a slight premium over Amazon's rates. All of the server configuration can be handled with zero human interaction. This simplifies hosting for app authors just as now, the difference being that it is now scalable. Also, using AWS plays to the current paradigm of having all data cached in RAM.
So, is AppJet the next web framework? Could it be something bigger?
No comments:
Post a Comment