Angular 2.0 Syndrome
| ←Older revision | Revision as of 02:40, 11 December 2025 | ||
| Line 5: | Line 5: | ||
=== [[Angular]] 2.0 Syndrome === | === [[Angular]] 2.0 Syndrome === | ||
| - | [[Angular]] used to be | + | [[Angular]] used to be quite a successful framework with all symptoms of a [[Good Technology]]: |
* backed by a huge company | * backed by a huge company | ||
* providing modern [[MVVM]] paradigm | * providing modern [[MVVM]] paradigm | ||
Summary
| ←Older revision | Revision as of 05:27, 24 August 2025 | ||
| Line 29: | Line 29: | ||
=== Summary === | === Summary === | ||
| - | When designing a framework, ''questioning loyalty'' is exactly the | + | When designing a framework, ''questioning loyalty'' is exactly the feeling you don't want your existing users to get! When we were designing the [[NetBeans Platform]], we paid a lot of attention to [[BackwardCompatibility]]. Because the last question we wanted our existing users to ask was: Should we try to switch to [[Eclipse]] RCP? |
Angular 2.0 Syndrome
| ←Older revision | Revision as of 05:26, 24 August 2025 | ||
| Line 27: | Line 27: | ||
* or they were thrown away and rewritten to [[React]] or co. | * or they were thrown away and rewritten to [[React]] or co. | ||
| - | + | === Summary === | |
When designing a framework, ''questioning loyalty'' is exactly the question you don't want your existing users to ask! When we were designing the [[NetBeans Platform]], we paid a lot of attention to [[BackwardCompatibility]]. Because the last question we wanted our existing users to ask was: Should we try to switch to [[Eclipse]] RCP? | When designing a framework, ''questioning loyalty'' is exactly the question you don't want your existing users to ask! When we were designing the [[NetBeans Platform]], we paid a lot of attention to [[BackwardCompatibility]]. Because the last question we wanted our existing users to ask was: Should we try to switch to [[Eclipse]] RCP? | ||
Angular 2.0 Syndrome
| ←Older revision | Revision as of 05:26, 24 August 2025 | ||
| Line 27: | Line 27: | ||
* or they were thrown away and rewritten to [[React]] or co. | * or they were thrown away and rewritten to [[React]] or co. | ||
| - | + | ### Summary | |
| - | + | When designing a framework, ''questioning loyalty'' is exactly the question you don't want your existing users to ask! When we were designing the [[NetBeans Platform]], we paid a lot of attention to [[BackwardCompatibility]]. Because the last question we wanted our existing users to ask was: Should we try to switch to [[Eclipse]] RCP? | |
| - | When we were designing the [[NetBeans Platform]], we paid a lot of attention to [[BackwardCompatibility]]. Because the last question we wanted our existing users to ask was: Should we try to switch to [[Eclipse]] RCP? | + | |
Angular 2.0 Syndrome
| ←Older revision | Revision as of 05:25, 24 August 2025 | ||
| Line 21: | Line 21: | ||
** reputation of [[Angular]] was damaged | ** reputation of [[Angular]] was damaged | ||
** new projects seeking for modern web framework started to seek for alternatives | ** new projects seeking for modern web framework started to seek for alternatives | ||
| - | ** [[React]] was a natural [[Good Technology]] (also backed by a huge company, [[Good Technology| | + | ** [[React]] was a natural [[Good Technology]] (also backed by a huge company, with a sense of [[Good Technology|coolness]]) choice |
* because of all the upgrade pain loyalty of previous users disappeared | * because of all the upgrade pain loyalty of previous users disappeared | ||
** when it is as complex to upgrade as completely rewrite why not try [[React]]? | ** when it is as complex to upgrade as completely rewrite why not try [[React]]? | ||
Angular 2.0 Syndrome
| ←Older revision | Revision as of 05:24, 24 August 2025 | ||
| Line 20: | Line 20: | ||
** the word about lack of [[BackwardCompatibility]] of [[Angular]] got out | ** the word about lack of [[BackwardCompatibility]] of [[Angular]] got out | ||
** reputation of [[Angular]] was damaged | ** reputation of [[Angular]] was damaged | ||
| - | ** new projects seeking for modern web framework | + | ** new projects seeking for modern web framework started to seek for alternatives |
| + | ** [[React]] was a natural [[Good Technology]] (also backed by a huge company, [[Good Technology|cool]]) choice | ||
* because of all the upgrade pain loyalty of previous users disappeared | * because of all the upgrade pain loyalty of previous users disappeared | ||
** when it is as complex to upgrade as completely rewrite why not try [[React]]? | ** when it is as complex to upgrade as completely rewrite why not try [[React]]? | ||
Angular 2.0 Syndrome
| ←Older revision | Revision as of 05:19, 24 August 2025 | ||
| Line 8: | Line 8: | ||
* backed by a huge company | * backed by a huge company | ||
* providing modern [[MVVM]] paradigm | * providing modern [[MVVM]] paradigm | ||
| - | * | + | * increasing developer productivity thanks to testing being built in since beginning |
'''Well setup for future growth''' as [[I]] like to say! Who could have envisioned [[Angular]] to loose its position completely? These days there is '''no buzz''' about [[Angular]]. Just [[React]], [[Vue.js]] and few ''like to be followers'' ([[Svelte]] is one [[I]] noticed). What has happened to [[Angular]]? | '''Well setup for future growth''' as [[I]] like to say! Who could have envisioned [[Angular]] to loose its position completely? These days there is '''no buzz''' about [[Angular]]. Just [[React]], [[Vue.js]] and few ''like to be followers'' ([[Svelte]] is one [[I]] noticed). What has happened to [[Angular]]? | ||
Angular 2.0 Syndrome
| ←Older revision | Revision as of 05:19, 24 August 2025 | ||
| Line 5: | Line 5: | ||
=== [[Angular]] 2.0 Syndrome === | === [[Angular]] 2.0 Syndrome === | ||
| - | [[Angular]] | + | [[Angular]] used to be a quite successful framework with all symptoms of a [[Good Technology]]: |
* backed by a huge company | * backed by a huge company | ||
* providing modern [[MVVM]] paradigm | * providing modern [[MVVM]] paradigm | ||
Angular 2.0 Syndrom
| ←Older revision | Revision as of 05:17, 24 August 2025 | ||
| Line 3: | Line 3: | ||
While [[Knockout.js]] is focused and lightweight framework, [[Angular.js]] tries to solve everything (kind of like [[Spring]] in [[Java]] - e.g. bloated beyond repair) - you either need to use it all, or none. As a result the [[Bck2Brwsr]] project decided to prefer [[Knockout.js]]. | While [[Knockout.js]] is focused and lightweight framework, [[Angular.js]] tries to solve everything (kind of like [[Spring]] in [[Java]] - e.g. bloated beyond repair) - you either need to use it all, or none. As a result the [[Bck2Brwsr]] project decided to prefer [[Knockout.js]]. | ||
| - | === [[Angular]] 2.0 | + | === [[Angular]] 2.0 Syndrome === |
[[Angular]] was quite successful with all symptoms of a [[Good Technology]]: | [[Angular]] was quite successful with all symptoms of a [[Good Technology]]: | ||
Angular 2.0 Syndrom
| ←Older revision | Revision as of 05:14, 24 August 2025 | ||
| Line 26: | Line 26: | ||
* or they were thrown away and rewritten to [[React]] or co. | * or they were thrown away and rewritten to [[React]] or co. | ||
| - | When designing a framework, | + | When designing a framework, ''questioning loyalty'' is exactly the question you don't want your existing users to ask! |
When we were designing the [[NetBeans Platform]], we paid a lot of attention to [[BackwardCompatibility]]. Because the last question we wanted our existing users to ask was: Should we try to switch to [[Eclipse]] RCP? | When we were designing the [[NetBeans Platform]], we paid a lot of attention to [[BackwardCompatibility]]. Because the last question we wanted our existing users to ask was: Should we try to switch to [[Eclipse]] RCP? | ||