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

Web Components with Mozilla’s Brick and X-Tag

hacks.mozilla.org

Post reply on HN
Print view View original

1–10 of 10 posts

Re: Web Components with Mozilla’s Brick and X-Tag

#3

Post by codepo8-hn »

aravindet wrote: post #2

How does this compare with the Polymer project?

X-Tag leverages the joint polyfill Google is the general maintainer of (Mozilla contribute code to it). It's the same one at the base of the Polymer stack.

Polymer, in comparison to Brick has a much more ambitious approach to being the framework to build apps with instead of aiding the creation of apps. Comparable with Dojo or .NET instead of jQuery.

Re: Web Components with Mozilla’s Brick and X-Tag

#5

Post by tyleregeto »

Looks really great, Polymer has always felt a little heavy to me. Brick seems like it would fit in my workflow better. Web components are going to be revolutionary for the web, I can't wait until we can start leveraging them.

I don't see any mention of browser support?

Re: Web Components with Mozilla’s Brick and X-Tag

#6

Post by spankalee »

codepo8-hn wrote: post #3
aravindet wrote: post #2

How does this compare with the Polymer project?

X-Tag leverages the joint polyfill Google is the general maintainer of (Mozilla contribute code to it). It's the same one at the base of the Polymer stack. Polymer, in comparison to Brick has a much more ambitious approach to being the framework to build apps with instead of aiding the creation of apps. Comparable with Dojo or .NET instead of jQuery.

I don't think that's really true about Polymer. It's still just a framework for creating custom elements. What features are you thinking of to compare to Dojo?

The big difference that I see is the template binding portion of Polymer which allows you to define an elements markup with data-binding template sort of like Angular.

Re: Web Components with Mozilla’s Brick and X-Tag

#7

Post by codepo8-hn »

spankalee wrote: post #6
codepo8-hn wrote: post #3

Earlier quoted context omitted.

X-Tag leverages the joint polyfill Google is the general maintainer of (Mozilla contribute code to it). It's the same one at the base of the Polymer stack. Polymer, in comparison to Brick has a much more ambitious approach to being the framework to build apps with instead of aiding the creation of apps. Comparable with Dojo or .NET instead of jQuery.

I don't think that's really true about Polymer. It's still just a framework for creating custom elements. What features are you thinking of to compare to Dojo? The big difference that I see is the template binding portion of Polymer which allows you to define an elements markup with data-binding template sort of like Angular.

Yes, very true. I was a bit fast answering this earlier. So far, there are no data-bindings in Brick.

Re: Web Components with Mozilla’s Brick and X-Tag

#10

Post by ebidel »

tyleregeto wrote: post #5

Looks really great, Polymer has always felt a little heavy to me. Brick seems like it would fit in my workflow better. Web components are going to be revolutionary for the web, I can't wait until we can start leveraging them. I don't see any mention of browser support?

Can you explain why it feels heavy? I would love to know more.

Polymer's entire stack is a la carte:

* platform.js - polyfills if you just want to use vanilla web component apis, today

* polymer.js - build declarative custom elements that use data-binding, touch, property observation, inheritance

* elements (ui/non-ui) - if you don't want to write any code at all :)

Sugaring libraries like Brick and Polymer that sit on top of the native web component APIs will, of course, be opinionated and do things a bit differently. However, the workflow for consuming components will be similar across the board. Something like `bower install brick-carousel polymer-tabs`. Then use the elements in your pages.

Post reply on HN