LM Blog - Latest Comments

Re: Closures in Javascript

Nicole Lee — Wed, 17 Oct 2012 22:15:06 -0000

joy fax server

Re: Closures in Javascript

Nicole Lee — Wed, 17 Oct 2012 22:14:30 -0000

Great help to me,
thank you.

Re: Kamikaze Marketing

MartinC00011 — Tue, 16 Nov 2010 06:11:04 -0000

The App Store represents an excellent model for how to charge for products.

Re: Closures in Javascript

David Semeria — Wed, 20 Oct 2010 05:20:56 -0000

Well - spotted J (as the initial). Will fix when I unearth the original document....

Re: New Video: Mixing and Sharing Images in Twiggler

Admin — Sun, 03 Oct 2010 15:41:44 -0000

I love this Twiggler.....it is becoming increasingly obvious that Twitter is now 'The' information source of the happening people online. We even see our pols tweeting from the Congress floor.
Your app should be climbing the charts of must haves.

Http://clickmaxim.com

Re: Closures in Javascript

J (as the initial) — Fri, 02 Jul 2010 04:45:34 -0000

Great slide, learned a lot, thanks.
Seems to have a typo on page 34 and after, "e.childNodes.length[i].onclick" should read "e.childNodes[i].onclick"
and in this particuliar example, childNodes would return the spans and their inner text, so alerts would display "1", "3" and "5"

Re: Kamikaze Marketing

johannabrooke — Mon, 28 Jun 2010 07:05:35 -0000

@ fredwilson The free trial will not work in my opinion, because one will use that and after will say that is not satisfied and look elsewhere and so on. To work, the micropayments should ensure the quality and the originality of the product.
Johanna @ blair rewards.com

Re: Closures in Javascript

David Semeria — Fri, 05 Mar 2010 09:31:38 -0000

Well done Mark, I don't think we broke the rules, either.

Re: Closures in Javascript

Mark Essel — Fri, 05 Mar 2010 09:28:57 -0000

We rule

Re: Closures in Javascript

David Semeria — Fri, 05 Mar 2010 09:17:58 -0000

The Steganography game: too easy!

Re: Freemium - Shmeemium

David Semeria — Sun, 28 Feb 2010 06:47:31 -0000

Thanks for your comment Kirk.

My point is very straightforward: you can charge 3% of your active client base $10/month, or you can charge 100% of them on average 30¢/month. The underlying economics of the business remain unchanged, with users still being able to try the product for free (up to a certain level of usage).

My subsequent post Kamikaze Marketing goes into a bit more detail on how the benefits of the free part of freemium can still be had without incurring the burden of subscriptions.

Re: Freemium - Shmeemium

KirkWard — Fri, 26 Feb 2010 17:29:27 -0000

I disagree with your point that the price of the premium service has to be set artificially high. The cost of acquiring the free subscriber and enticing them to stay subscribed is the same cost any marketer would have in building a list. Cost of acquisition plus cost of maintenance. You point that freemium is a marketing model is most apt.

Re: Closures in Javascript

Mark Essel — Mon, 22 Feb 2010 21:39:05 -0000

Got to p26 after making a pretty wild visual replacement to the flash on VM and getting ready for sleep. One take away from playing with jQuery, Chrome (and likely other webkit optimized browsers) handle javascript incredibly faster than firefox. The good news, Chrome frame should work for all.

(this is my poor man's bookmark to pick this up next time)

Re: Closures in Javascript

David Semeria — Mon, 22 Feb 2010 08:49:10 -0000

Cheers Mark.

Re: Closures in Javascript

Mark Essel — Mon, 22 Feb 2010 08:46:43 -0000

Will forward this along to my hacker/coder friends. Thanks David!

Re: Freemium - Shmeemium

David Semeria — Wed, 03 Feb 2010 11:52:51 -0000

Thanks very much Tom!

Sure, as I mentioned above, it's a self-fulfilling prophecy. Generally roll-outs like this can work when users perceive genuine value and so are more willing overcome their unwillingness to change habits.

It's happened many times before. Off the top of my head, I might suggest when Excel came from nowhere and caused Lotus 123 users to change their behaviour. They only did this because the benefits of using Excel far outweighed the burden of its learning curve.

The switch to micro-billing involves significantly less pain (if any). The key is that people should really value the benefits.

Re: Freemium - Shmeemium

tom piamenta — Tue, 02 Feb 2010 10:33:09 -0000

Very interesting!
If microbilling reaches critical mass a snow ball effect can follow, but "educating" the market, to gain this mass, could be quite ... well, impossible?
thanks for a great post!

Re: New Video: Mixing and Sharing Images in Twiggler

gisnap — Wed, 23 Dec 2009 06:27:42 -0000

Its really cool, I came to know this really worth visiting, just bookmarked your site.

http://gisnap.com/
The place where fun never ends

Re: Chrome OS - when pull is better than push

contractor web design — Sat, 05 Dec 2009 01:52:25 -0000

chrome is a headache! been using it for a few days and uninstall it!! :(

Re: The Mixable Web (2)

Mark Essel — Fri, 16 Oct 2009 16:59:32 -0000

A very impressive example of identifying meta data with images and extra data format, interoperability. I look forward to learning more about the structure and development using LM. Thanks David.

Re: The Mixable Web (1)

David Semeria — Sat, 12 Sep 2009 15:58:06 -0000

Sridharan, thanks for your very kind words.

I took a long look at your website, and I think it's very interesting. The great advantage of your approach is that a component is able to access other frameworks/libraries, for example JQuery. LM's architecture also allows this type of approach, but, to be honest, it's quite inefficient. There is a lot of overlap between the core functionality in LM's generic library and what many of these external libraries provide. Also, LM's core library is optimized for LM's own internal generic data structures and methods.

In future posts we'll see how using generic data structures along with generic libraries to manipulate them lies at the heart of LM's architecture - it is this which permits the micro-component model to deliver highly complex applications in such an efficient manner, and allow these applications to be combined and re-combined into new applications.

Thanks very much for stopping by, and I'll be paying attention to your site in the future.

Re: The Mixable Web (1)

David Semeria — Sat, 12 Sep 2009 15:15:53 -0000

For the moment, the server-side code is written in PHP, but that will probably change in the release version. I realize that it's practically impossible to fully grasp how the architecture works given the very high-level description in this post. The subsequent posts should gradually rectify this.

Again, you hit on a key issue when you talk about the tension between the generic nature of a component and the ability to customize it for particular use cases. Future posts will address this issue, but for the time being all I can say is the architecture has several ways of 'abstracting away' the differences between specific (customized) instances of the same component, and then reconstituting in the browser the specific component instance from the generic definition (I hope this makes some sense).

Re: The Mixable Web (1)

Sridharan_Srinivasan — Sat, 12 Sep 2009 14:39:33 -0000

Your concepts and your blog information are awesome.

I have been working / researching during my free time on something like this where applications can be built from components. My hypothesis was to test whether assembly separated/distinct from coding of an application leads to reduced complexity/increased flexibility since my focus was on reducing my pain and customer pain in executing large enterprise application developments.

But my approach was more generic in that I don’t have any basic components, what I did was abstract the connections of the components as a language of assembly and hence built a generic framework which in theory can assemble any components using a simple generic language of assembly.

I found that my language of assembly consists of 4 simple metadata, namely, specifying a context, adding components into the context, configuring components into the context and linking components into the context which can lead in theory to assembly oriented application development.

I created a proof of concept web site which was fully assembled from standalone components which helped me to prove it can works, but still need to test it on complex data driven applications or even use it as you are doing to accept data from multiple streams.

I am currently in the process of testing in a limited way whether it can used to develop a proof of concept for a large enterprise application for the architecture industry which I am currently developing for a client.

If you have time and can check my proof of concept website www.arshu.com on my approach to solving the complexity/flexibility of web application and give me your comments, i will be greatfull.

Re: The Mixable Web (1)

Magnus Wikegård — Sat, 12 Sep 2009 14:03:02 -0000

Hi David,
I wish I had read more before I made the my comment. As you mentioned I was thinking of larger components. Now when I read further it seems to be a PHP framework.
I have allways liked generic code in it's right places. When designing systems I try to see customer requirements as special cases of a generic solution. When abstracted enough perhaps several use cases can be solved with one generic design. I know this isn't by the book with regard of some of the Agile thoughts but it works.
I think it is extremenly important to analyse/split what is custom and what is configuration of generic/standard otherwise customisation will spread through the system when it should have been configuration.
I will follow this closely with great interest.

Re: The Mixable Web (1)

David Semeria — Sat, 12 Sep 2009 08:50:07 -0000

Unfortunately, LM is not yet ready to be thrown into the wild, even in a pre-alpha state. However, when it is released, we're quietly confident that it will generate some interest. Remember, LM is the only web framework with a built-in revenue model.....