I am an old fashioned software developer. Experience has taught me that complex frameworks sooner or later tend to become a burden and break up applications.
When using frameworks (and other tools) I must be able to understand them to a sufficiently decent level. I must be able to find and fix problems (so it must be open source). If I can’t then this framework is too complex for me.
When I checkout and build Joplin I end up with 105280 files. This is, by my definition, unmaintainable. You can argue that a lot of these files are from Electron and other 3rd party packages, but each of these packages can stop functioning any time and don’t tell me that they won’t because there are big companies/user groups backing them. Electron broke Joplin several times and Laurent cs. did a great job overcoming incompatible changes far as possible. Some problems were never fixed so we just have to get used to it. That’s a nice, custom-friendly attitude from big companies/user groups, isn’t it?
Also, many of these are pulled in from 3rd party sites during the build/install. I can never be sure it will be the same collection of files that I’m testing.
So, as you may guess, I’m very sceptical about those modern quick start-up frameworks, be it Electron or Haxe or whatever. In the beginning you make good progress because they make things easier for you, but you may regret it later when you are 80% done and unable to complete the final 20% since the framework won’t let you.
So it is better to minimize framework dependency than to swap one framework for yet another.