|
by Entropy Stew 10/19/2017, 10:19pm PDT |
|
|
|
|
|
Rafiki wrote:
Now that I've gotten further into the class, it's pretty much just a small framework for building in-browser applications.
You're the only person I've heard refer to Angular as a "small framework". It's fuckhuge! 2 way data binding also makes for ponderous flow.
I compared it to MVC because I was seeing a ton of similarities where they accomplish the exact same things, but MVC projects are for more traditional websites serving individual pages and a traditional navigation model. I think a better comparison now would be to XBAPs. Exact same concept (embedded browser application), but not relying on a third party framework or browser plugin (and not as restricted or deprecated). And as Shnibble alluded to below, it has the same drawback of being an embedded application: you have a big-ass up-front download to download the "application" files.
It is an MVC project, but entirely contained in the browser, and the server is relegated to some kind of additional model that has to be queried and synced up with via api calls or a websocket or graphql or whateverthefuck. It's just turned the web page into a thicc client instead of a dumb terminal.
So I guess if I had the need for a browser app I'd go with it, but I can't see using it for a traditional site.
Angular will code the everloving shit out of your basic control panel app, which is probably 98% of big enterprise apps, which are probably an overwhelming majority of the lines of code out there.
-/ES/- |
|
|
|
|
|
|
|