Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Introducing Aurelia

blog.durandal.io

Post reply on HN
Print view View original

31–40 of 87 posts

Re: Introducing Aurelia

#31

Post by bronson »

ZenoArrow wrote: post #27
bronson wrote: post #22

Earlier quoted context omitted.

I missed it too. Got a link or something? Or do you mean the hint that some of the code can run server-side? That seems obvious, and is not in itself isomorphism.

In that case, we need to establish what isomorphism is. What's your definition?

We probably agree on what "isomorphism" is, but maybe not "support"?

If a platform claims to support isomorphism, I expect it to render server-side with zero drama/workarounds/blog posts. Support means that producing fully-rendered html is a core part of the product and documentation, not something glued on the side or pieces to reassemble on your own.

From the wording, it looks like Aurelia isn't there yet?

Re: Introducing Aurelia

#32

Post by netfire »

Looks interesting. It would be nice if they were more specific about what browsers the framework supports though. There's a phrase that you can "Leverage the technology of the future but target today's Evergreen Browsers." That's a nice bit of copywriting, but it doesn't instantly tell me which browsers are supported. It would be nice to have an official supported list.

Re: Introducing Aurelia

#33

Post by shruubi »

I hate to sound jaded and cynical, but am I the only one who feels weird about a new framework announcement containing information for getting training and consulting? I understand that there is no money in releasing free frameworks, but it seems a little soon to be selling consulting and training on an early-access preview...

Re: Introducing Aurelia

#34

Post by Linell »

This seems really nice. Just looking through the first few links and pages, it seems to have all of the nice things I enjoy about Angular. It looks like it may have less of a learning curve too, which would be very nice.

Re: Introducing Aurelia

#35

Post by optimusclimb »

YET. ANOTHER. Javascript framework.

This is what people are talking about in countless blog posts (that also make their way to the front page of HN.)

So glad I'm not a front end dev trying to keep up with this world.

Re: Introducing Aurelia

#36

Post by i_am_ralpht »

ZenoArrow wrote: post #28
brentvatne wrote: post #20

Earlier quoted context omitted.

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.

What are the main differences between the shadow DOM and the virtual DOM?

Shadow DOM is a DOM structure that's hidden under a tag (for example, the tag has a Shadow DOM which provides the controls and timecode UI).

Virtual DOM is (typically) a pure JavaScript object-based DOM representation that gets somehow flushed to actual DOM (or to WebGL or anything else). You as the programmer use the Virtual DOM directly and try to avoid talking to the real DOM underneath. Virtual DOM has a few advantages, but the one that stands out in today's browsers is limiting DOM thrashing where you query the DOM (requiring an expensive recalc) and then modify the DOM (invalidating what was recalc'd) in a loop.

Re: Introducing Aurelia

#37

Post by huragok »

optimusclimb wrote: post #35

YET. ANOTHER. Javascript framework. This is what people are talking about in countless blog posts (that also make their way to the front page of HN.) So glad I'm not a front end dev trying to keep up with this world.

Same can be said for Ruby, Python, C#, etc. A lot of people have a lot of ideas, preferences and time to burn creating/learning new client side frameworks.

Re: Introducing Aurelia

#38

Post by hardwaresofton »

shruubi wrote: post #33

I hate to sound jaded and cynical, but am I the only one who feels weird about a new framework announcement containing information for getting training and consulting? I understand that there is no money in releasing free frameworks, but it seems a little soon to be selling consulting and training on an early-access preview...

I think this might have something to do with the fact that he is the CTO of Durandal (which seems to be based off of durandal.io, or maybe the other way around).

I assume that he's currently the CTO of a very small company (of maybe even just him), and one of the ways to do that profitably, while building things you love, is to consult/provide training on the things that you have built that others want to use

Re: Introducing Aurelia

#39

Post by hardwaresofton »

bronson wrote: post #25

The video, the intro, the docs, ... None of them seem to mention testing. That's a disappointment. Anyone got a link on how to test an Aurelia app?

http://phantomjs.org/

http://jasmine.github.io/

Not trying to snark, but if you need to test javascript, use jasmine. If you want to acceptance/integration testing (depending on your definition of those terms) as a user clicking around your site to make sure the things you think happen are actually happening, use phantomjs (I'd also suggest using nightmarejs on top)

Re: Introducing Aurelia

#40

Post by judah »

optimusclimb wrote: post #35

YET. ANOTHER. Javascript framework. This is what people are talking about in countless blog posts (that also make their way to the front page of HN.) So glad I'm not a front end dev trying to keep up with this world.

There are two sides to it: yes, new frameworks and new stuff to learn, and that can be overwhelming.

On the other hand, rapid evolution leads to better ideas, keeps your mind fresh as your learning never ceases, and an opportunity to improve yourself, keep your career in demand, and generate more income for yourself.

Example: when I started web dev, client-side code was basically a giant function containing browser-specific DOM manipulation.

Today, client-side code is arranged in modules with single responsibility, well-defined application architecture, easy to test, easy to modify or extend, the app logic cleanly separated from the UI.

Rapid evolution also keeps the mind fresh. You're continually learning new concepts, absorbing new ideas. This helps me enjoy my job; I'm always learning.

Rapid evolution keeps my skills in demand, too. My last 2 gigs have been because I learned Angular. I'd be hard-pressed to find work if I was still building web apps like it was 1998.

Post reply on HN