[web2py] Re: LAMP like frameworks are dying. Time for the javascript age
http://blog.mysyncpad.com/post/2073441622/node-js-vs-erlang-syncpads-experience On Apr 12, 12:45 pm, Albert Abril wrote: > Just a question... is erlang a direct competitor to javascript with this > paradigm? > > 2011/4/12 JmiXIII > > > > > > > > > "Expect the growth of more full-blown desktop-like > > apps hosted in the browser (like the Ext JS desktop demo). Expect > > people to begin to hate refreshing the page. " => +1 > > > I really agree with this and I wish so much webbrowser could use > > python as javascript > > > On 12 avr, 00:46, cjrh wrote: > > > On Apr 9, 10:35 am, Luther Goh Lu Feng wrote: > > > > > I hope to learn from everyone's opinion on this. > > > > It is pretty clear that the future belongs to javascript, as long as > > > that is the language that all browsers support. Expect javascript > > > JITs to improve. Expect the growth of more full-blown desktop-like > > > apps hosted in the browser (like the Ext JS desktop demo). Expect > > > people to begin to hate refreshing the page. > > > > By including jQuery, web2py is ahead of the curve, or at least on par > > > with the other "traditional" frameworks. We could probably make AJAX > > > even easier if we tried. We probably should try. More support for > > > reducing page refreshes.
Re: [web2py] Re: LAMP like frameworks are dying. Time for the javascript age
Just a question... is erlang a direct competitor to javascript with this paradigm? 2011/4/12 JmiXIII > "Expect the growth of more full-blown desktop-like > apps hosted in the browser (like the Ext JS desktop demo). Expect > people to begin to hate refreshing the page. " => +1 > > I really agree with this and I wish so much webbrowser could use > python as javascript > > > > On 12 avr, 00:46, cjrh wrote: > > On Apr 9, 10:35 am, Luther Goh Lu Feng wrote: > > > > > I hope to learn from everyone's opinion on this. > > > > It is pretty clear that the future belongs to javascript, as long as > > that is the language that all browsers support. Expect javascript > > JITs to improve. Expect the growth of more full-blown desktop-like > > apps hosted in the browser (like the Ext JS desktop demo). Expect > > people to begin to hate refreshing the page. > > > > By including jQuery, web2py is ahead of the curve, or at least on par > > with the other "traditional" frameworks. We could probably make AJAX > > even easier if we tried. We probably should try. More support for > > reducing page refreshes. >
[web2py] Re: LAMP like frameworks are dying. Time for the javascript age
"Expect the growth of more full-blown desktop-like apps hosted in the browser (like the Ext JS desktop demo). Expect people to begin to hate refreshing the page. " => +1 I really agree with this and I wish so much webbrowser could use python as javascript On 12 avr, 00:46, cjrh wrote: > On Apr 9, 10:35 am, Luther Goh Lu Feng wrote: > > > I hope to learn from everyone's opinion on this. > > It is pretty clear that the future belongs to javascript, as long as > that is the language that all browsers support. Expect javascript > JITs to improve. Expect the growth of more full-blown desktop-like > apps hosted in the browser (like the Ext JS desktop demo). Expect > people to begin to hate refreshing the page. > > By including jQuery, web2py is ahead of the curve, or at least on par > with the other "traditional" frameworks. We could probably make AJAX > even easier if we tried. We probably should try. More support for > reducing page refreshes.
[web2py] Re: LAMP like frameworks are dying. Time for the javascript age
On Apr 9, 10:35 am, Luther Goh Lu Feng wrote: > I hope to learn from everyone's opinion on this. It is pretty clear that the future belongs to javascript, as long as that is the language that all browsers support. Expect javascript JITs to improve. Expect the growth of more full-blown desktop-like apps hosted in the browser (like the Ext JS desktop demo). Expect people to begin to hate refreshing the page. By including jQuery, web2py is ahead of the curve, or at least on par with the other "traditional" frameworks. We could probably make AJAX even easier if we tried. We probably should try. More support for reducing page refreshes.
[web2py] Re: LAMP like frameworks are dying. Time for the javascript age
I think node.js is fantastic. It is not a serverside framework and JS is still not that friendly compared to python but for some applications node.js is really fast. Erlang is better though. On Apr 9, 3:35 am, Luther Goh Lu Feng wrote: > I got this link off twitter, and would like to share this article with > the community as I felt that it is a good read for web developers. > > http://metamarketsgroup.com/blog/node-js-and-the-javascript-age/ > > "Three months ago, we decided to tear down the framework we were using > for our dashboard, Python’s Django, and rebuild it entirely in server- > side Javascript, using node.js." > > "The Javascript age is about event streams. Modern web pages are not > pages, they are event-driven applications through which information > moves. The core content vessel of the web — the document object model > — still exists, but not as HTML markup. The DOM is an in-memory, > efficiently-encoded data structure generated by Javascript." > > I hope to learn from everyone's opinion on this.
[web2py] Re: LAMP like frameworks are dying. Time for the javascript age
I tend to agree that LAMP will thrive for quite some time. But node.js and the article are interesting. The one thing I have witnessed with good success is returning tabular data as JSON and then using JavaScript to render the . We used YUI for this with good results. We could easily return thousands of rows and then create tables that had real-time sorting, filtering and paging. In general, JavaScript does seem like a reasonable choice at the server level (although I still prefer Python syntax). I'm still not a fan of some of the "event streaming". It definitely makes sense in some situations. But I still like most things to have an address.
[web2py] Re: LAMP like frameworks are dying. Time for the javascript age
I think the author is still in the honeymoon with his newly found love: Node.js. After the honeymoon, he will realize that the LAMP stack is not only dead, it'll be around and kicking for a long time to come. The same is uncertain for "javascript frameworks", which will find their places nonetheless. On Apr 9, 3:35 am, Luther Goh Lu Feng wrote: > I got this link off twitter, and would like to share this article with > the community as I felt that it is a good read for web developers. > > http://metamarketsgroup.com/blog/node-js-and-the-javascript-age/ > > "Three months ago, we decided to tear down the framework we were using > for our dashboard, Python’s Django, and rebuild it entirely in server- > side Javascript, using node.js." > > "The Javascript age is about event streams. Modern web pages are not > pages, they are event-driven applications through which information > moves. The core content vessel of the web — the document object model > — still exists, but not as HTML markup. The DOM is an in-memory, > efficiently-encoded data structure generated by Javascript." > > I hope to learn from everyone's opinion on this.
