Read this to get some context
Step 1.
What is esri's billions $$$ grave mistake they made 15 years ago?
Esri made a very wrong decision in 2010 to use a open source third party javascript frame work "dojo" as their Arcgis javascript API's as back-bone !!!
https://dojotoolkit.org/
Step 2.
How long this mistake last?
This grave mistake has not been correct since 2010 (v3.00), until 2025 Feb v4.33 (release)
2025 Feb v4.33 (release) marked ESRI finally abandon "dojo" after 15 years.
Esri let arcgis JS API's consumer suffer this pain for 15 years long. ( I have been complaining this pain since 2015 )
I don't believe it is consumer(us) triggered this change, (they seems don't care user's feeling by changing api all the time.)
Esri must encounter something from manufacture's side that is intolerable, unendurable for them, triggered they finally abandon dojo.
https://developers.arcgis.com/javascript/latest/breaking-changes/
Step 3.
what is significant consequences ?
This api break through change will cause thousands of US gov's web map application break down in the coming years if they don't fix it.
Which comes with billions of billions $$$ lose ( tax payer will pay the price ), in either way.
You upgrade it, need extra million $$$.
You don't upgrade, you lose previous invested million $$$, since it will stop working.
Step 4.
esri's bad excuse is weak, unconvincing, unbelievable to justify this grave mistake, grave failure.
https://www.esri.com/arcgis-blog/products/js-api-arcgis/developers/javascript-maps-sdk-a-full-transition-to-components
Step 5.
dojo js framework is esri SDK's back-bone !!! come on, esri.
If I open any esri map, you will see "dojo" in their source code, dojo is esri SDK api's back- bone !
esri's developper their so-called "widget" is build on top of dojo framework.
Every widget is made of dojo.
If I open any of the widget, you will see "dojo" !!! come on, esri.
Step 6.
If I open any esri map, you will see "dojo" in their source code, dojo is esri SDK api's back- bone !
https://geocarenavigator.hrsa.gov/?page=Home
Step 7.
widget is made of dojo, any widget is build on dojo
Step 8.
If I open any esri map, you will see "dojo" in their source code, dojo is esri SDK api's back- bone https://gis.stackexchange.com/questions/325480/what-is-jimu-js-in-web-appbuilder
Step 9.
come on, esri, 15 years ago, you told consumer, why use dojo, 15 years late, you do not admit you use dojo
https://developers.arcgis.com/javascript/3/jshelp/inside_dojo.html
Step 10.
come on, esri, 15 years ago, you told consumer, why use dojo, 15 years late, you do not admit you use dojo before?
https://developers.arcgis.com/javascript/3/jshelp/why_dojo.html
Step 11.
Why consumer complaining 'dojo' since 15 years ago?
The biggest problem I have with dojo is I always have to write require block at the first line of code.
Then write thousands of functions, ten thousands lines of code inside of this block.
This eliminate the possibility of code sharing. 1 same function, you have to write 100 times in 100 files. If you want to change a single char, you have to change 100 times in 100 files. Consumer has been suffer this pain for 15 years. Esri seems don't care consumer.
Step 12.
2025 v4.33 the real breaking through change is not widget to component.
The real breaking through change is ESRI finally abandon 'dojo'
And ESRI do not publicly even mention this in any where !
widget is part of dojo.
Since esri abandon dojo, widget is of course will go away.
Component is just replacement for what widget does before.
If esri admit abandon dojo, that means esri admit their grave mistake 15 years ago, they will be responsible for billions of billions $$$ tax money lose.
To get rid of responsibility, esri keep silent, while do the change silently.
ESRI can ignore consumer, since consumer don't have a second choice in GIS market today.
Step 13.
Google map api did not change since 2009 ! If you write a google map in 2009, it will still runs like a new in 2025 !
Google map api don't use 3rd party open source software as their back-bone.
Microsoft map api don't use 3rd party open source software as their back-bone.
HereMap api don't use 3rd party open source software as their back-bone.
Mapbox api don't use 3rd party open source software as their back-bone.
Apple map api don't use 3rd party open source software as their back-bone.
ESRI is the only one make this mistake ! Now they get away with it.
Step 14.
Step 15.
Step 16.
Step 17.
Step 18.
Step 19.
Step 20.