=== Summary ===

=== 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 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?

* or they were thrown away and rewritten to [[React]] or co.

* or they were thrown away and rewritten to [[React]] or co.

### Summary

=== 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?

* 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, ''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?

** 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|cool]]) choice

** [[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]]?

** 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 rather started to prefer [[React]]

** 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]]?

* backed by a huge company

* backed by a huge company

* providing modern [[MVVM]] paradigm

* providing modern [[MVVM]] paradigm

* increased productivity thanks to testing being the primary focus

* 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 ===

=== [[Angular]] 2.0 Syndrome ===

[[Angular]] was quite successful with all symptoms of a [[Good Technology]]:

[[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

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 Syndrom ===

=== [[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]]:

* 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, the last question is exactly the question you don't want your existing users to ask!

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?

* 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]]?

When designing a framework, the last question is exactly the question you don't want your existing users to ask!

When designing a framework, the last question is exactly the question you don't want your existing users to ask!