6 ms·

Angular is different. It is not concerned with the server side at all. It's just about so-called Single Page Applications. This SPA would typically talk to ser

by fuzzy2 10y ago

Angular is different. It is not concerned with the server side at all. It's just about so-called Single Page Applications. This SPA would typically talk to services via "AJAX" (though probably with JSON). These services could be implemented using any technology.

rocky1138 10y ago
This still doesn't describe how Angular is objectively "better." In fact, because it requires Javascript just to render HTML, it is objectively worse than straight up HTML delivered from a server-side solution.
- fuzzy2 10y ago
  > This still doesn't describe how Angular is objectively "better." Of course. Because it isn’t. It’s not worse either. It’s different. It’s a completely different approach to creating web applications. Everyone has different criteria to meet. Working without JavaScript usually isn’t one with modern web applications.
  - ianamartin 10y ago
    To be clear, I don't eschew JavaScript. Of course you need that for applications. JS stuff goes into a Mako template where I import and call the JS when I need it. This has the added benefit of extremely small page sizes. Nothing gets loaded globally. Every page has only and exactly what it needs to function properly. I'm just wondering if I am that much of a dinosaur and I need to invest the time into learning some of these frameworks to be competitive on the market in the future. What I do works well. It's fast, it's scalable, and I'm very fast at developing with that toolchain. The code is clean, clear, well-organized, and modular. Anyone who knows Python, SQL(Alchemy), and JavaScript can pick it up and work with it. I can work on any different part of an application without worrying about if it might break something elsewhere. I feel like the patterns I've gotten comfortable with are kind of a sweet spot between micro-services and monolithic. My apps are technically monoliths, but the various modules are clearly isolated. I'm in my late 30s now, and I want to keep up and not turn into one of those old guys who refuses to stay current. I'm genuinely curious what the value proposition is, outside of learning a new paradigm for its own sake. There's always value in learning new ways to solve problems you already have a good handle on. But outside of those things, is there some secret magic I'm missing out on?

by fuzzy2 10y ago

rocky1138 10y ago

This still doesn't describe how Angular is objectively "better." In fact, because it requires Javascript just to render HTML, it is objectively worse than straight up HTML delivered from a server-side solution.

fuzzy2 10y ago
> This still doesn't describe how Angular is objectively "better." Of course. Because it isn’t. It’s not worse either. It’s different. It’s a completely different approach to creating web applications. Everyone has different criteria to meet. Working without JavaScript usually isn’t one with modern web applications.
- ianamartin 10y ago
  To be clear, I don't eschew JavaScript. Of course you need that for applications. JS stuff goes into a Mako template where I import and call the JS when I need it. This has the added benefit of extremely small page sizes. Nothing gets loaded globally. Every page has only and exactly what it needs to function properly. I'm just wondering if I am that much of a dinosaur and I need to invest the time into learning some of these frameworks to be competitive on the market in the future. What I do works well. It's fast, it's scalable, and I'm very fast at developing with that toolchain. The code is clean, clear, well-organized, and modular. Anyone who knows Python, SQL(Alchemy), and JavaScript can pick it up and work with it. I can work on any different part of an application without worrying about if it might break something elsewhere. I feel like the patterns I've gotten comfortable with are kind of a sweet spot between micro-services and monolithic. My apps are technically monoliths, but the various modules are clearly isolated. I'm in my late 30s now, and I want to keep up and not turn into one of those old guys who refuses to stay current. I'm genuinely curious what the value proposition is, outside of learning a new paradigm for its own sake. There's always value in learning new ways to solve problems you already have a good handle on. But outside of those things, is there some secret magic I'm missing out on?