you know, i really found this article to be educational also, because i've seen it before where someone will post a leak of some sort, a leaked build, or leaked screen shots, something leaked, and they will say 'wow look it's so rough man this will be the worst most horrible experience ever' or 'look they cut this essential feature out it will be horrible' or 'look how sloppy everything is!'. from what i read of this dev's statements, he sounds like me when i'm working on anything, from my car to my computer. if an outsider peeked in and looked at it all while i'm in the middle it may look really sloppy. dirt all over, parts strew right and left, half of it doesn't even work, and i myself am just sloppy and dirty. dust on my nose, smudges on my glasses, grease on my hands. it really presents the idea that i am just a slob and also that the finished product will be horribly broken.
of course, that is the not the case. i just need to get dirty and make a mess to get anywhere sometimes. i may wind up taking whole sections of my computer or car out and botching something together just to test something. it doesn't look good at all, but it's just part of the process. when i'm done, it will be functional. it will work. it will in fact even look nice, but i have my process to work in and if you step into that while i'm busy and you don't know what is going on in my head, you won't be impressed.
so please, save the hating on this dev for someone else. i'm glad he said something. it helps put these negative reviews of various Windows leaked builds (or WIP builds of anything really) in perspective. important things to realise i figure.
thanks, anonymous dev.