Live data from Hacker News

Aurelia UX

blog.aurelia.io

11–20 of 35 posts

Re: Aurelia UX

#12
> Documentation:

> Forthcoming...

I feel like introducing something without documentation is a little premature. Or maybe its use is abundantly clear to those who've used Aurelia.

Re: Aurelia UX

#13

Our team has been using Aurelia for many months. While it has some cool features, there are plenty of gotchas that add a lot of overhead. Weeks spent on features that had to be reworked due to edge cases in DI, for example, or relying on some of the non-core packages. It's interesting stuff, but don't jump into it expecting to run at full speed without tripping a few times along the way.

This is a pre-alpha release. So, those adopting it should be prepared to deal with regular breaking changes.

Calling Component Authors

We know we've got a ton of members within our community who have built and want to build components for Aurelia. We're inviting you to join with our core team to build out the components of the Aurelia UX library.

Re: Aurelia UX

#15

Our team has been using Aurelia for many months. While it has some cool features, there are plenty of gotchas that add a lot of overhead. Weeks spent on features that had to be reworked due to edge cases in DI, for example, or relying on some of the non-core packages. It's interesting stuff, but don't jump into it expecting to run at full speed without tripping a few times along the way.

I have the same experience, We have been using it for months and I cannot say that we are happy. A lot of bugs, a lot of missing documentation, a lot of bloat, and some bad breaking changes. It seems to me that the Aurelia team wants to do too many thing at once, and cannot deliver to the standards that other framework provide. It's sad because the underlying ideas are good. It is in many ways similar to Vue.js, whic…

Aurelia is arguably more mature than vue though I guess that depends on who you ask. Can you reference any bugs? Currently most issues that are open on the main repositories are feature requests or edge cases

Re: Aurelia UX

#16

Our team has been using Aurelia for many months. While it has some cool features, there are plenty of gotchas that add a lot of overhead. Weeks spent on features that had to be reworked due to edge cases in DI, for example, or relying on some of the non-core packages. It's interesting stuff, but don't jump into it expecting to run at full speed without tripping a few times along the way.

Can you give some examples on edge cases with DI? Most things that don't work well with DI are due to bad patterns that just need a better resolving strategy which are available or customizable

Re: Aurelia UX

#18
Am I the only one that finds its kinda weird that they'd announce a UI/UX framework without a live previews? That's really one of the killer features of the web, that you can show stuff off without installing anything.

Re: Aurelia UX

#19
post #11

Decent grid widget that let's me get rid of ExtJS included?

Depending on what you mean by grid, you might find react-virtualized [0] interesting. [0] https://bvaughn.github.io/react-virtualized/

Major flaw with that component: the scroll handle size does not change. So if you have 10,000 rows, moving the handle down by one pixel will take you from entry #0 to ~#40. In fact, somewhere between 10k and 100k, it stops being possible to scroll to some elements, say from #0 to #20, whether using the wheel or the scrollbar.

Re: Aurelia UX

#20

Am I the only one that finds its kinda weird that they'd announce a UI/UX framework without a live previews? That's really one of the killer features of the web, that you can show stuff off without installing anything.

Agreed, all the way at the bottom they almost seem to have a link to examples, but then it turns out that it's just a repo of examples that you can clone and serve yourself.

It definitely seems like they're missing a huge part of what's going to sell this framework without functioning examples online.

Post reply on HN