Why Aurelia Struggles to Gain Popularity


#101

Thanks for the reply. If there are problems running Aurelia on stackblitz, then this says more about Aurelia than stackblitz. (however I don’t think this should be the case, and we should have an Aurelia stack available, and we should have a big button on the front page) Either way, if we are going to “prefer” codesandbox.io, that’s fine, but we should NOT be leaving behind stackblitz (and others like it).

As a front-end developer, the more places I go and I see Aurelia (right up front like I see Angular), the more it will help Aurelia gain popularity with the general population. I think there needs to be a dedicated effort to have Aurelia sit side-by-side Angular on all of these sites, not just stackblitz.com


#102

Let’s separate performance from functionality. I wouldn’t want to see an example of the nice else syntax in the midst of 200 lines of super-fast virtual list sorting code. That mixes the message of simplicity and usability with that of complexity.
As I mentioned earlier, the cheat-sheet was an absolutely awesome source of assistance. I pushed and pushed for a moderated forum system like this about three years ago, to capture the enormous sample and advice knowledge-base that so many people were giving in the Gitter channel and collate that into an FAQ style repository, but it just didn’t happen. I suspect that is now part of our acceptability issue.

Perhaps a sensible thing would be to have a simple app with hundreds or thousands of snippets. I search for “binding” and see a list on the left with one-way, two-way, custom, properties, ref, etc. and clicking on one shows a simple code snippet on the right. Not a huge project, just a snippet like we have in the cheat-sheet.
As with any advanced framework, it’s too difficult to search through thousands of pages of doco to find a basic feature, and let’s be honest, when people do a Google search for “Aurelia accessing a DOM element”, the first match is a Stack Overflow answer, and the second a link to a 404 page error on the official doco.
Very few searches expose the official documentation, and the search feature in the doco pages on the hub is no Google.
We have the option to include a link to GistRun (or whatever the current monthly favourite sandbox environment is), but that’s not essential for most snippets. I think the key thing is to create a set of examples that are a pyramid of complexity, with five hundred really simple snippets of one or two lines, and a decreasing number of more complex examples for people to move up to as their skills improve and requirements are realised.


#103

I think @jsobell is right. I’ve been using Aurelia since it was Durandal. Even having used it for so long there are times that I just need an example of functionality to “refresh my memory” so I know exactly how to use it. A google search usually takes me to stack overflow, and sometimes the answers there are out-dated.

In an ideal world, I should be able to come to the doc site, start typing what I’m looking for and like Google, immediately see headlines along with small-text showing the exact context/syntax I need on how to use or interact with any piece of the framework I have searched for.

I should be able to quickly scroll through the headlines until I see my exact use case or something that matches what I’m looking for. Once I’ve found the area I’m looking for I should be able to click to see all the various ways, starting from beginner to advanced, of achieving what I’m trying to do within this particular space.

More of an interactive cheat-sheet, that is the be-all, end-all, authoritative source for Aurelia. Always up to date and not just for syntax, but also best practices, patterns, starting from the surface and going all the way down to the low-level API usage etc. i.e. @jsobell’s thousands of snippets, where each snippet is the bare minimal example showing off the particular subject matter.

For as long as I’ve been using Aurelia, I feel like the low-level functionality (where Aurelia really hides its power) is put off and not very clear on how to really maximize the low-level bits. I.e. while the document site gives me examples of how to use or do something basic, the API side really is just for reference and doesn’t really show examples of how to interact with low-level bits constructively. (For this I would need to look into the source code and try to figure out what this piece of API actually does and when/where to use it etc… who has time for that?)

The new documentation site should be a place where the beginning user could gravitate towards simple use cases (binding/else/ref/etc), and the advanced user could learn how to use Aurelia at very low levels to achieve those really cool advanced use cases; all of it laid out in such a way that the user could snap code examples together like Lego bricks quickly achieve what we’re trying to do with Aurelia (regardless of complexity).

I think a first-class documentation site along these lines would go a long way towards increasing the popularity of Aurelia. I think opening up the low-level bits would increase community involvement. Make it easy for me as a developer to get in, get out, all the while making it super easy for me to contribute.

Along this vein, I could also see something like bootsnipp.com but for Aurelia where a user can search for and find higher-ordered components, generators, attributes, plug-ins, etc. as a way to help speed up Aurelia development. With a rich resource like this, enterprises and devs alike would flock to Aurelia.

– And why not. It’s like that old commercial for Rolaids… “How do you spell Awesome… A.U.R.E.L.I.A”