OK, I admit it! I loved the Clint Eastwood “spaghetti westerns” (not telling you how old I am, but I saw them when they were originally released.) One of my favorites is “The Good, The Bad and the Ugly”. I am fairly new to the Sencha universe (going like gangbusters for 2-3 months) Let me give you my analysis of this using this movie as a model:
· The Bad: It is obvious that Sencha’s core compentency is their technical prowess (It is obvious that they get a F- in sales, since trying to talk to someone prior to the purchase was like pulling teeth. I still have not heard back from anyone re: the training classes after many emails and phone calls. But I am getting off topic). The downside of having such a large and rich library, is that the use is not intuitive. Thank God for all of the 3rd party books, However, a detailed overview of the features / uses / positioning of the library would help.
· The Ugly: No Ugly, actually I am very impressed with the product
· The Good: Forget good! The grid control is GREAT! Of course, I am coming from Flex where the grid control was sort of an embarrassment (wait, strike sort of!) For those of us who live and die by a powerful / flexible grid control, this is the cat’s meow! (My focus is building data-centric business applications, 99.9% of what I am doing will either be a grid or a form.)
· The Good: umm…errrr.. Well there is a LOT of it! And if you know where to search, you might find an answer. (which many times, required me to scan over all of the methods of multiple classes to get an answer.)
· The bad: It is NOT complete, it is NOT always accurate, There are way way way too few examples. When I look up a method (or property) It would be very helpful to see a code snippet or 2
· The Ugly: When responding to comments re: the quality of the documentation, it seems that Sencha is imitating an Ostrich (head in sand, pretending nothing really matters). Comments are sent back to the users, “we are doing better” , “just wait and see”, poppycock! Tell us how many MORE people are doing the documentation! Give us dates and milestones when we might see some improvement
· The Good: There is an example for most everything, The depth of examples is impressive. This has saved me many hours of development.
· The Bad: Since the examples are there for teaching / guiding, it would be nice to have comments within the source code.
· The Ugly: The geniuses @ Sencha seem to think there is only one “right” way to do anything, In many cases there are more than one way. Having some examples that
· The Good: If you can embrace, if you can “grok” the architect workflow and methodology (its not Eclipse with a plugin!), it is VERY fast, efficient, keeps you from making some stupid errors, and is super for those who have not yet memorized all 194 methods for the DirectStore class, etc. (if you don’t know what GROK means, stop reading this post, go to your favorite book store (or amazon) and purchase and read Robert Heinlein’s: “Stranger in a strange land”)
· The Bad: forget bad, go right to ugly!
· The Ugly: While your application can be edited in an external editor, someone, MUST write a program that will read and parse a folder and generate the appropriate metadata to import the folder into Architect. This is #1, much more important (IMHO) than any of the features that are being added to version 3.
· The Good: One stop shopping, will not use the word mature (see The Bad below), but will say this an established, reputable company with a complete solution to both desktop and mobile. I have not found a company that comes close.
· The Bad I feel like Sencha is run by very smart 18 yr olds who have the attention span of umm.errr. an 18 year old. Products / Ideas show up, are worked on, then seem to go into a corner and gather dust (and spider webs). I look at Sencha Devs which is a joke. It could be very useful for those who want / need to find 3rd parties to help (offload) development, but the searching is abysmal, the comments are ALL the same for each company. Sencha Marketplace is not dead, but thinking it might be on life support. If you guys are making a profit, how about you assign some manpower (woman power?) to improving and marketing some of these very neglected features.
· The Ugly: No ugly. If the company was ugly, I would not have given up sleep for the last 60 days, trying to get my arms around the Sencha ecosphere.)