XExzfaZi

1At first I thought Flutter would be lovely to use and I can enjoy working with it. But I ended up learning that it's an over engineered framework that makes life miserable the same way Java or Angular.js was. I pulled a lot of hair and all nighter going thru their shitty code (one of their example project has a home.dart with over 1000LOC containing 25 different classes: https://github.com/flutter/samples/blob/master/gallery/lib/pages/home.dart).
2
3API doc sucks, the same way Java doc class was. I ended up digging thru their source instead of the API doc lol. The technical docs barely has example, while the available example seemed to be made by intern as they are basic and cluttered. A key indicator that it was made by intern tho, was the liberal use of magic number instead of using basic math. I.e, they would subtract 44px from the container's height for one special list which has 1 less item compared to the other lists, instead of simply multiply the item count with the height of each item.
4
5Hot-reload feature barely work. It feels like 2014 with early browersync or the Android Studio app sync when it first came out. A simple style change often causes the whole app to re-render with state reset.
6
7The current debugger console is trash. On breakpoint or crash, it throws error then stack trace, then never print a summary of the error. This 2009 behavior result in a lot of effort crawling thru the log. There are times it would start the stack trace at the framework source, not my source, and that took a lot of time to figure out what went wrong. These stuff should only happens in C++ with DLL, not some modern "open source" app framework lol. In summary, the dev experience atm feels like a corporate job - slow, grindy, over-engineered - that it kills my flow. 
8
9The amount of code needed to do anything seems verbose and repetitive. It reminds me of Java SpringBoot. It's coding for the shake of coding, not problem solving. (https://samatkinson.com/why-i-hate-spring/ ).