Title: Supporting a huge number of similar applications; Supporting software production lines (SPLs) · Issue #21352 · angular/angular · GitHub
Open Graph Title: Supporting a huge number of similar applications; Supporting software production lines (SPLs) · Issue #21352 · angular/angular
X Title: Supporting a huge number of similar applications; Supporting software production lines (SPLs) · Issue #21352 · angular/angular
Description: I'm submitting a... [x] Feature request Current behavior When you want to create one web app using Angular, everything is superb and excellent. But as soon as you start to use it to the benefit of a company that has a software production...
Open Graph Description: I'm submitting a... [x] Feature request Current behavior When you want to create one web app using Angular, everything is superb and excellent. But as soon as you start to use it to the benefit of ...
X Description: I'm submitting a... [x] Feature request Current behavior When you want to create one web app using Angular, everything is superb and excellent. But as soon as you start to use it to the benefit...
Opengraph URL: https://github.com/angular/angular/issues/21352
X: @github
Domain: github.com
{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Supporting a huge number of similar applications; Supporting software production lines (SPLs)","articleBody":"## I'm submitting a...\r\n[x] Feature request\r\n\r\n## Current behavior\r\nWhen you want to create one web app using Angular, everything is superb and excellent. But as soon as you start to use it to the benefit of a company that has a software production line (SPL), things get a little ugly.\r\nFor example, in AngularJS, the old school of web meant referencing JavaScript files directly in HTML head section, and lazy loading each HTML fragment (roughly equivalent to Angular Component) and its relevant JavaScript file. This could be reused and automated in a bigger context, with AngularJS truly serving a good role in the bigger picture and providing true business-value for the company.\r\nBased on three reasons we decided to move to Angular:\r\n\r\n- Fear of AngularJS being deprecated and discontinued (proactive approach towards technology change)\r\n- Simpler component definition (the concept of Scope in Angular JS is so tricky and not mature)\r\n- Market trend to recruit new developers (local issue of course, yet applicable)\r\n\r\nHowever, we suffered tremendously to harness Angular's power for our own benefits. Because as soon as you start deviating from Angular's opinionated everything, you literally encounter tons of problems. \r\nHere are some examples:\r\n\r\n- When we want to create 10 applications per month, and they are all in a similar business context, the very deeper concept of IoC in the field of configuration and preparation creates business value. Instead of each developer and each project controlling its configuration and preparation, we tend to configure them and prepare them all from a bigger context (SPL). For example, in AngularJS we would only ask a developer to create a simple folder, and then create HTML and JS files for features of that application immediately based on our OWN convention and without any extra step. Yet here in Angular as soon as we create a new project tens of configuration and preparation files are created (package.json, package-lock.json, tsconfig.json, tslint.json, karma.conf.js, polyfill.ts, ....) and they can easily deviate from the same files across projects, which is so expensive in the sense of an SPL.\r\nFor example we need to have one project.json file, that is somehow inherited across 500+ projects. One polyfill.ts file that is not even repeated across projects and developers won't see it.\r\n\r\n- We need to use our own file-system architecture, which is different from Angular's architecture. Folder naming, folder nesting, component naming and similar other things\r\n\r\n- We don't want to load an entire Module, rather we need to load each component separately. That is if you navigate to another route, we need to load that route's component on the fly and lazily. We don't want to create a module per component to load modules lazily\r\n\r\n- We don't want to use TypeScript as our first-citizen scripting language. It's bloated with boilerplate code (specially those imports at the top and all those decorators and exports at the end of each file and ...). We want to write the minimal JavaScript truly related to that component's logic very briefly.\r\n\r\n- We don't want to use Webpack. We want to load Angular from one CDN, load Material from another CDN, our shared components from yet another CDN to increase speed of loading, not a bloated huge big file created via Webpack that packs them all together per app.\r\n\r\n## Expected behavior\r\n\r\nAngular being more flexible to the old school of web and old standards of writing web applications, and introducing new features only as additions, not replacements.\r\n\r\n## Minimal reproduction of the problem with instructions\r\nTry to think about creating 500+ similar applications using Angular, with as lesser budget and dollars spent as you can imagine, so that you can reduce the end cost for customers through productivity. That means lesser configuration, lesser boilerplate code, lesser technologies involved, using old familiar tools and technologies, etc.\r\n\r\n## What is the motivation / use case for changing the behavior?\r\nBusiness value is the one of the most important drives in the industry. Angular is so great when it comes to create ONE SINGLE ad-hoc application. TBH, I think it's the best for that scenario.\r\nYet its power can't be harnessed (or maybe we don't know how) to support frequency of production.\r\n\r\nAngular version: 5\r\n\r\nThank you so much. If the given context is not clear, I would be glad to provide more details through examples and comparisons.\r\n ","author":{"url":"https://github.com/Nefcanto","@type":"Person","name":"Nefcanto"},"datePublished":"2018-01-06T04:51:25Z","url":"https://github.com/angular/angular/issues/21352"}
| react-profiling | 0 |
| react-import-map | react,react-dom,react-dom/client,react-dom/profiling,react-is,react/compiler-runtime,react/jsx-dev-runtime,react/jsx-runtime,scheduler@b8488ee2c322 |
| route-pattern | /_view_fragments/issues/show/:user_id/:repository/:id/issue_layout(.:format) |
| route-controller | voltron_issues_fragments |
| route-action | issue_layout |
| fetch-nonce | v2:8c5e2006-83df-003b-32b3-6a76bc38dbc5 |
| current-catalog-service-hash | 81bb79d38c15960b92d99bca9288a9108c7a47b18f2423d0f6438c5b7bcd2114 |
| request-id | E74E:229B2E:D53F2E:11AB0F3:6B00F8F9 |
| html-safe-nonce | 12a5dd66b25d61130dd23aa64db84fbce222eb44ac41cbded810f4109ab384eb |
| visitor-payload | eyJyZWZlcnJlciI6IiIsInJlcXVlc3RfaWQiOiJFNzRFOjIyOUIyRTpENTNGMkU6MTFBQjBGMzo2QjAwRjhGOSIsInZpc2l0b3JfaWQiOiI1ODYxMTYwNjAxNTUxNjk4MTY5IiwicmVnaW9uX2VkZ2UiOiJpYWQiLCJyZWdpb25fcmVuZGVyIjoiaWFkIn0= |
| visitor-hmac | 1ec60b0ad607c2aa1e255f4461f6d5b7689a6ff1fc73bebc7cba7f88a87c6639 |
| hovercard-subject-tag | issue:286459523 |
| github-keyboard-shortcuts | repository,issues,copilot |
| google-site-verification | Apib7-x98H0j5cPqHWwSMm6dNU4GmODRoqxLiDzdx9I |
| octolytics-url | https://collector.github.com/github/collect |
| analytics-location | / |
| fb:app_id | 1401488693436528 |
| apple-itunes-app | app-id=1477376905, app-argument=https://github.com/_view_fragments/issues/show/angular/angular/21352/issue_layout |
| twitter:image | https://opengraph.githubassets.com/975d32cb8629dfb585b5a06fa95d079320b8337324e2305b55b9226ee0bea04f/angular/angular/issues/21352 |
| twitter:card | summary_large_image |
| og:image | https://opengraph.githubassets.com/975d32cb8629dfb585b5a06fa95d079320b8337324e2305b55b9226ee0bea04f/angular/angular/issues/21352 |
| og:image:alt | I'm submitting a... [x] Feature request Current behavior When you want to create one web app using Angular, everything is superb and excellent. But as soon as you start to use it to the benefit of ... |
| og:image:width | 1200 |
| og:image:height | 600 |
| og:site_name | GitHub |
| og:type | object |
| og:author:username | Nefcanto |
| hostname | github.com |
| expected-hostname | github.com |
| None | e208d86428ec00a57ade75058166297440e8128a01e5287c31a53dc042bbf187 |
| turbo-cache-control | no-preview |
| go-import | github.com/angular/angular git https://github.com/angular/angular.git |
| octolytics-dimension-user_id | 139426 |
| octolytics-dimension-user_login | angular |
| octolytics-dimension-repository_id | 24195339 |
| octolytics-dimension-repository_nwo | angular/angular |
| octolytics-dimension-repository_public | true |
| octolytics-dimension-repository_is_fork | false |
| octolytics-dimension-repository_network_root_id | 24195339 |
| octolytics-dimension-repository_network_root_nwo | angular/angular |
| turbo-body-classes | logged-out env-production page-responsive |
| disable-turbo | false |
| browser-stats-url | https://api.github.com/_private/browser/stats |
| browser-errors-url | https://api.github.com/_private/browser/errors |
| release | 7dafd017fb7809a839c443dba08622af38e63c09 |
| ui-target | canary-2 |
| theme-color | #1e2327 |
| color-scheme | light dark |
| react-app-name | issues |
Links:
Viewport: width=device-width