- From: Andrea Rendine <master.skywalker.88@gmail.com>
- Date: Thu, 2 Apr 2015 22:19:09 +0200
- To: Bobby Mozumder <mozumder@futureclaw.com>
- Cc: WHATWG <whatwg@lists.whatwg.org>
You don't have to show any magnificent markup example with pages of description. You have to show authors how this framework WORKS in real life. With comprehensive use cases. This is a polyfill. As you can find for any other "HTML magic" you see around. CSS is a different case. Without proper tools, you can only replicate your desired layout with graphical tools (and this is always done). You can't expect that UA vendors build a new product based on your words. Do you have ideas about several use cases and not just one? Build a JS surrogate (you said you know JS) mimicking what future user agents are expected to do. And test it for security and robustness and flexibility. Markup is just words. Tagged words, but simply words. Of course browser vendors will have to do a lot of programming to reproduce your ideas. But first show how your ideas work. And keep in mind that something is not simple just because it starts with < and ends with >, and for this reason you can call it markup or XML or SGML or HTML and say it's simple. Ok, it's you on the right side and the whole world gone wrong. I'm sure your proposal has gone viral, and the fact you have no contributors, no forks or no answers on Github (apart from Taylor Swift spam) is just red herring. But with a demo, everything will be clearer. And stop criticizing everybody else's work just because it's different from yours. Cheers. 2015-04-02 21:27 GMT+02:00 Bobby Mozumder <mozumder@futureclaw.com>: > > On Apr 2, 2015, at 3:22 PM, Rimantas Liubertas <rimantas@gmail.com> > wrote: > > > >>> There are fundamental problems with your proposal, namely: > >>> 1) it relies on some undefined magic > >> > >> I believe that’s called “programming”. > > > > So that poor fashion designer will have to learn to program after all… > > The browser vendors are the ones doing the programming. They’ll > ultimately decide if they want to implement this or not. > > >>> 2) it changes HTML to something entirely different. > >> > >> To what? HTML already has things like <SCRIPT> and other features not > related to hypertext markup. > > > > I don’t know to what, I never saw any examples how your MVC would look > like. > > Would you care to show how something like > http://backbonejs.org/docs/todos.html would look if > > done your way? > > I have examples in the original message, as well as in: http:/// > www.github.com/mozumder/HTML6 > > -bobby > --- > Bobby Mozumder > Editor-in-Chief > FutureClaw Magazine > mozumder@futureclaw.com <mailto:mozumder@futureclaw.com> > +1-240-745-5287 > www.futureclaw.com <http://www.futureclaw.com/> > twitter.com/futureclaw <https://www.twitter.com/futureclaw> > www.linkedin.com/in/mozumder <http://www.linkedin.com/in/mozumder> >
Received on Thursday, 2 April 2015 20:19:35 UTC