40 karma · joined October 13, 2014
The fact that one has to learn mind numbing levels of abstractions, contortions, domain specific knowledge, virtual DOM's and all this with the hindsight that this could soon be out the door just like any number of mootools, extJS's before it. All this effort to get a SPA or a smoother UX interaction doesn't seem to be as appealing.
Given that the basic UX functionality can be achieved with plain html and js in a fraction of the time and effort (minus the smoothness) since the ~2010's.
Like you rightly stated in the previous para, I cannot disagree more with this statement.
eInk like passive displays are in a league of their own compared to active displays even if it is Apple who is making those.
The main issue is not that I give you X amount of time now please fix it coz you have generous time now.
The cost of such a change is ENORMOUS.
As an example, in a recently IPO'd company we had a team of engineers and we had 6 months of work for 10 engineers, round the clock, to fix the Python 2 to Python 3 migration issues alone! and the original creators of the code were long gone! .. and I could only imagine the plight of thousands of other folks in similar boats and other resource constrained boat-less entities!
Then there are distributed packages and libraries that are used by a large set of audience that are dev complete and no longer maintained as such. The cost of fixing those are much much higher.
It makes one more than wince at the thought of going through this exercise again.
Now I have two Ubuntu 20.04 laptops - Toshiba SatellitePro and Dell Inspiron. Windows 10 broke the Toshiba touchpad and wouldn't upgrade from 8.1 without fits, seizures and loss of data. With Snap I was able to port most of my MS Office and other windows software.
TBH, Dell did have issues around the infamous Nvidia display drivers that would freeze the screen needing a hard reboot. But at least my laptops are able to bounce back to enjoy the rest of their natural life!