Live data from Hacker News

Introducing Aurelia

blog.durandal.io

11–20 of 87 posts

Re: Introducing Aurelia

#11
post #2

So this is why he bailed on the Angular team?

He wrote a blog post explaining his reasons for leaving: http://eisenbergeffect.bluespire.com/leaving-angular/

"I am not saying that Angular 2.0 is going to be a bad framework. What I am saying is that it is no longer fundamentally the same thing I was originally hired to help build nor is it compatible with my vision for the future. It is no longer the best path ahead for the existing Durandal community and it also isn't the best choice for anyone who has used my other frameworks and wishes to migrate to the web."

Re: Introducing Aurelia

#13
post #5

My wife's name is Aurelia and its really weird to see a web framework named this. Its like naming a framework: "Thomas". Example: Me: What tools/framework did you use to build the app? You: Aurelia. Me: Oh cool, I used Thomas. You: Yeah, I thought about using Thomas, but stuck with Aurelia because it offered better features.

One ex-colleague of mine is named Aurelia and I got the same reaction.

Re: Introducing Aurelia

#14

This looks a bit like Angular 1.3 and 2.0 to me - DI, binding and repeats look like ng-model and ng-repeat.. I'm curious to see more when the full docs are out though. No mention of isomorphism or a virtual DOM, seems to be a bit behind the zeitgeist.

I don't know why you missed it, but it mentions both isomorphism (code that can be run client side or server side) and the virtual DOM (web components, etc...).

Correct me if I'm wrong but web components can use the native DOM without depending on a virtual DOM.

Re: Introducing Aurelia

#15
I'm excited to see this. Durandal was (and actually still is) a joy to use and coming up with something this advanced with a possible migration path is amazing.

Small confusion: They chose to use 6to5 and jspm but jspm depends on Traceur and there is even an issue[1] for supporting 6to5 on jspm issue tracker. (Edit: Just discovered that they were answering questions on Gitter[2])

[1]: https://github.com/jspm/jspm-cli/issues/354 [2]: https://gitter.im/Aurelia/Discuss

Re: Introducing Aurelia

#16
post #5

My wife's name is Aurelia and its really weird to see a web framework named this. Its like naming a framework: "Thomas". Example: Me: What tools/framework did you use to build the app? You: Aurelia. Me: Oh cool, I used Thomas. You: Yeah, I thought about using Thomas, but stuck with Aurelia because it offered better features.

My wife is named Julia. . . . And my brother is named Lisp, so it gets weird. :).

Less than a sibling called PHP though.

Re: Introducing Aurelia

#17
post #5

My wife's name is Aurelia and its really weird to see a web framework named this. Its like naming a framework: "Thomas". Example: Me: What tools/framework did you use to build the app? You: Aurelia. Me: Oh cool, I used Thomas. You: Yeah, I thought about using Thomas, but stuck with Aurelia because it offered better features.

My wife is named Julia. . . . And my brother is named Lisp, so it gets weird. :).

http://ars.userfriendly.org/cartoons/?id=20010831

(i've always wondered if their not recognising "miranda" as a language was a miss or a subtle joke on illiad's part)

Re: Introducing Aurelia

#19
post #5

My wife's name is Aurelia and its really weird to see a web framework named this. Its like naming a framework: "Thomas". Example: Me: What tools/framework did you use to build the app? You: Aurelia. Me: Oh cool, I used Thomas. You: Yeah, I thought about using Thomas, but stuck with Aurelia because it offered better features.

We make these jokes with the documentation for the Julia language.

"The easiest way to learn and experiment with Julia is by starting an interactive session".

Re: Introducing Aurelia

#20

This looks a bit like Angular 1.3 and 2.0 to me - DI, binding and repeats look like ng-model and ng-repeat.. I'm curious to see more when the full docs are out though. No mention of isomorphism or a virtual DOM, seems to be a bit behind the zeitgeist.

I don't know why you missed it, but it mentions both isomorphism (code that can be run client side or server side) and the virtual DOM (web components, etc...).

This is not mentioned in either the blog post or the docs, at least not easily findable with a cmd+f

"Use some of the libraries on the server with NodeJS. i.e. DI." - some, and I'd expect an explicit mentioning of isomorphism if it were possible at the moment to render it on the server side.

Shadow DOM != Virtual DOM. I mean the React-style Virtual DOM.

Post reply on HN