Timeline for How to structure a modern web application
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 8, 2013 at 10:04 | answer | added | Amit Kriplani | timeline score: 1 | |
| Aug 8, 2013 at 9:16 | comment | added | Lorenzo Dematté | Yes, absolutely: I am not criticizing jQuery, but the apps and examples built (mis)using it, that make it difficult to learn how to use it properly (and choose what to use it for). I will definitely look at KnockoutJS, thank you. | |
| Aug 8, 2013 at 8:56 | comment | added | Benjamin Gruenbaum | WPF is in your profile so I gave it as an example. For WPF you should check KnockoutJS - similar notion of observables. A lot smaller than Angular (MVVM with just data binding) and assumes much less about your code structure, it has a similar notion of reusable view components too. There is plenty of bad jQuery code out there because jQuery is often the door to programming in general and in the web to many. We asked Resig about this in the JS room - I agree with his answer. | |
| Aug 8, 2013 at 8:54 | history | tweeted | twitter.com/#!/StackProgrammer/status/365395633865101312 | ||
| Aug 8, 2013 at 8:46 | comment | added | Lorenzo Dematté | Thanks for the "answer". Probably I am still failing to see the connection between native app development (which I did in both Qt and WPF) and web applications. I still consider them different worlds, and I worry too much about the differences to see the similarities...probably. And there are too many "bad" jQuery applications and examples out there, I suppose | |
| Aug 8, 2013 at 8:39 | comment | added | Benjamin Gruenbaum | In that case the answer is crystal clear. You should not even consider "control based", "the mix #1" and "the mix #2". "the mix #3" is the only one that makes any sense - it's how you'd structure an application in any other environment - be that Qt, WPF or pretty much anything. Server side HTML is useful when your data is loading from the server and in order to serve a quick response, after the initial phase a web app should behave like an application sould. MV* is a tried and tested approach for building GUI, not separating concerns can really hurt you. Still, test both and see for yourself. | |
| Aug 8, 2013 at 8:34 | comment | added | Lorenzo Dematté | Yes, I should made more clear that Angular is just used as an example of client-side MVVM/templating framework.. I have read that (excellent) Q&A when I built my Angular application, it was indeed a very good read! | |
| Aug 8, 2013 at 8:31 | comment | added | Benjamin Gruenbaum | Also, consider reading stackoverflow.com/questions/14994391/… | |
| Aug 8, 2013 at 8:26 | comment | added | Benjamin Gruenbaum | Using jQuery to 'enrich' HTML does not separate concerns at all. Separation of concerns in GUI is huge. I've seen this approach turn out as a huge problem multiple times creating huge, hard to maintain sphaghetti code bases. jQuery is just a library that does easy DOM manipulation and an AJAX facade - that's all it should be used for. Angular is not the only choice for an MV* framework - however it is a fair one. It enforces separation of concerns. Mix #3 sounds like the de-facto standard approach for web apps. | |
| Aug 8, 2013 at 8:11 | review | Close votes | |||
| Aug 13, 2013 at 14:25 | |||||
| Aug 8, 2013 at 8:07 | answer | added | Ben McDougall | timeline score: 3 | |
| Aug 8, 2013 at 7:44 | history | asked | Lorenzo Dematté | CC BY-SA 3.0 |