On famo.us, semantic html and the future for web apps

Now with famo.us being out of private beta and the code being online I was eager to take a closer look.

I stumbled over this talk by Steve Newcomb the CEO of famo.us.

It’s *super* interesting to watch this stuff. Go watch it!

It would be very interesting to take some time to play with famo.us sometime soon. What’s interesting though is that it’s an entirely different paradigm than what AngularJS, Polymer, vue.js or even WebComponents are after.

They basically say that the gaming industry got rendering right (minute 43:35), and and the web industry got everything else right and they are trying to combine it. They don’t believe in semantically correct HTML for web apps. They say this stuff is for documents and no one should care about it building web apps. That’s also what Sencha is telling people.

It’s interesting and a part of me agrees with that. On the other hand, HTML is awesome for designers to work with. People even start building things *outside the browser* (think: githubs Atom editor) with web technology *because* of HTML/CSS.

I remember that working with Sencha was a pain from a designers perspective *because* you work very decoupled from the underlying HTML.

It really seems people are strongly divided about the direction the web is taking. Google seems to strongly believe in semantic html and to enrich it for web apps. Angular, Polymer, vue.js, WebComponents are all projects strongly driven by Google. From the perspective of a company driven by ad sales this makes perfect sense. Semantic markup has great value for Google as a search engine / ad selling company.

On the other hand there are companies like Apple, Sencha, Famo.us which do *not* believe this would be the right way forward.

I can’t say that I have a clear opinion about this stuff. Just that it’s an interesting observation.


2 thoughts on “On famo.us, semantic html and the future for web apps

  1. John says:

    I was really looking forward to working with Famo.us but the Terms of Service and other policies at the new Famo.us site seem rather demanding. Any person or company wanting to learn Famo.us has no choice it seems but to agree to these terms.
    Famo.us is a technology that is hardly out the door (in public beta) yet they are asking for your 100% agreement to a long list of constraints, all in their favour it seems.
    Does anyone else running a company building some unique software feel wary about the Famo.us terms? Will it hurt and limit a business or is this the norm these days?
    Why would such a fuss even be called for, seems rather preposterous. On the one hand their software is open source yet they want your arm and leg, or what?
    Is this something to be concerned about?

  2. Just some dude says:

    Famo.us is dying a slow horrible death. The web doesn’t want jQuery. That’s why we have Angular and Ember and Polymer and Backbone (and that list goes on an on). That’s the highlight of Famo.us…A loose collection of special effects. But everyone else is already doing that PLUS providing us with a solid framework in addition. How could Famo.us ever keep up? Especially considering they change their home page and story and direction all too often? Their web site just screams that they are fishing around ideas for something, but can’t find the target.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s