3 ms·

I have a policy of only shipping "back-end" apps because I'm worried about performance, browser compatibility and SEO. I don't know if the situation has improve

by Yuioup 7y ago

I have a policy of only shipping "back-end" apps because I'm worried about performance, browser compatibility and SEO. I don't know if the situation has improved in Angular 9. Does anybody here use Angular for their customer facing websites?

pjmlp 7y ago
We follow the pattern Java/.NET traditional BE stacks, Vue and Angular (on this order). So far I have only deployed Angular once in production for an IoT Dashboard. It was based on Material Dashboard, it was good enough for the monitoring use case, but it was for on-premises deployment.
- Yuioup 7y ago
  Yeah exactly. I do something similar (Angular, .NET Core) and use Angular for apps that the customer never sees.
jspash 7y ago
Have a look at Phoenix Live View -> https://www.youtube.com/watch?v=8xJzHq8ru0M https://www.youtube.com/watch?v=8xJzHq8ru0M It is still early days, and isn't suitable for every use-case, but it could be the answer you're looking for. Continue to write back-end code only. But with the benefits of quick-response front-end app. I'm a total convert (evangelist) who has been increasingly put off by the evolution (devolution?) of front-end development over the past 5-10 years. This could be one way of the mess.
- Yuioup 7y ago
  It's not Angular's architecture I have a problem with. As a former Delphi and current .NET developer, Angular fits like a glove, not to mention Typescript which was created by Anders Hejlsberg. It's the output I'm worried about. The HTML outputted by Angular pre-Ivy is verbose and runs very slow on old browsers (IE9, with polyfills). A customer facing website can be visited by anyone, from a tech savvy Linux user to your grandma which uses Internet Explorer and thinks Facebook is the internet. I don't want to face the wrath of clients who realize that their website is slow and non-optimized because I'm using Angular.
stopyellingatme 7y ago
We use Angular for the Alabama Dept of Forensic Science's DNA Tracker and the Alabama Dept of Public Accounts. Both seem to work well and have good performance.

by Yuioup 7y ago

pjmlp 7y ago

We follow the pattern Java/.NET traditional BE stacks, Vue and Angular (on this order). So far I have only deployed Angular once in production for an IoT Dashboard. It was based on Material Dashboard, it was good enough for the monitoring use case, but it was for on-premises deployment.

Yuioup 7y ago
Yeah exactly. I do something similar (Angular, .NET Core) and use Angular for apps that the customer never sees.

jspash 7y ago

Have a look at Phoenix Live View -> https://www.youtube.com/watch?v=8xJzHq8ru0M https://www.youtube.com/watch?v=8xJzHq8ru0M It is still early days, and isn't suitable for every use-case, but it could be the answer you're looking for. Continue to write back-end code only. But with the benefits of quick-response front-end app. I'm a total convert (evangelist) who has been increasingly put off by the evolution (devolution?) of front-end development over the past 5-10 years. This could be one way of the mess.

Yuioup 7y ago
It's not Angular's architecture I have a problem with. As a former Delphi and current .NET developer, Angular fits like a glove, not to mention Typescript which was created by Anders Hejlsberg. It's the output I'm worried about. The HTML outputted by Angular pre-Ivy is verbose and runs very slow on old browsers (IE9, with polyfills). A customer facing website can be visited by anyone, from a tech savvy Linux user to your grandma which uses Internet Explorer and thinks Facebook is the internet. I don't want to face the wrath of clients who realize that their website is slow and non-optimized because I'm using Angular.

stopyellingatme 7y ago

We use Angular for the Alabama Dept of Forensic Science's DNA Tracker and the Alabama Dept of Public Accounts. Both seem to work well and have good performance.