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

Ember's Glimmer Engine

github.com

Post reply on HN
Print view View original

81–90 of 136 posts

Re: Ember's Glimmer Engine

#81

Post by teraflop »

EdwardMSmith wrote: post #77
unknownian wrote: post #75

Earlier quoted context omitted.

That's not just what it says. If it just said that, that would be fine. It says making "any claim" against a Facebook patent will terminate your right to use the software. Facebook gets to protect its own software patents: "that any right in any patent claim of Facebook is invalid or unenforceable." The other lines are okay, it seems. I am not an IP law expert or lawyer though, but the writing seems pretty simple.

I'm not a lawyer either, but isn't the word "claim" a term of art in law. Doesn't it have a specific meaning distinct from the common usage?

"Claim" has a specific meaning in the sense of the invention "claimed" by a patent. But Facebook's patent grant is clearly not using it in that context: "any claim (including by filing any lawsuit, assertion or other action)".

Re: Ember's Glimmer Engine

#82

Post by cromwellian »

vjeux wrote: post #24

React 0.14 is going to have similar optimizations. Check those three posts if you are interested in the details :) Reuse Constant Value Types like ReactElement: https://github.com/facebook/react/issues/3226 Tagging ReactElements: https://github.com/facebook/react/issues/3227 Inline ReactElements: https://github.com/facebook/react/issues/3228

Basically, if you treat render functions as "pure functional" functions, you can employ memoization and avoid recalculation. I hope this isn't the subject of patents, because it seems pretty basic.

Re: Ember's Glimmer Engine

#83

Post by ralmidani »

teraflop wrote: post #81
EdwardMSmith wrote: post #77

Earlier quoted context omitted.

I'm not a lawyer either, but isn't the word "claim" a term of art in law. Doesn't it have a specific meaning distinct from the common usage?

"Claim" has a specific meaning in the sense of the invention "claimed" by a patent. But Facebook's patent grant is clearly not using it in that context: "any claim (including by filing any lawsuit, assertion or other action)".

And a good reason for someone to claim a patent is invalid is being sued for violating that patent.

Re: Ember's Glimmer Engine

#85

Post by peterhunt »

ralmidani wrote: post #73
teh wrote: post #71

Earlier quoted context omitted.

What makes the patent grant unfair? I think saying "you can use our pretty powerful technology until you sue us" is a great way to defang the patent system. [1] https://github.com/facebook/react/blob/master/PATENTS

It's unfair and one-sided because you cannot sue Facebook for infringing an unrelated patent, but if Facebook sues you for an unrelated patent, you will lose your rights if you try to assert (defensively) that their patent is invalid. In other words, you can never sue or even defend yourself against a Facebook lawsuit. For a more balanced approach to patents, see the GPL, Mozilla Public License, or Apache 2.0 License…

This is a common misinterpretation of this clause. There's been a lot of discussion at length here: https://news.ycombinator.com/item?id=8985722

Re: Ember's Glimmer Engine

#86

Post by tessierashpool »

colinramsay wrote: post #50
davexunit wrote: post #37

>building virtual DOM nodes for static areas of your markup that will never change for every change requires many more allocations and increases GC pressure. I'm not familiar with Ember, but why not just store the constant value in a variable to solve this problem? For example, in MithrilJS, you write templates in plain JavaScript, so I just stash large, static parts of the tree in variables and only rebuild vdom nod…

You appear to have been downvoted; while I don't know whether your potential solution is right or wrong your downvoters should have been polite enough to explain their reasoning.

I hope someone makes you an admin!

yesterday, I got downvoted repeatedly for mentioning that I hadn't seen an IIS header in years. ¯\_(ツ)_/¯

Re: Ember's Glimmer Engine

#87

Post by ralmidani »

peterhunt wrote: post #85
ralmidani wrote: post #73

Earlier quoted context omitted.

It's unfair and one-sided because you cannot sue Facebook for infringing an unrelated patent, but if Facebook sues you for an unrelated patent, you will lose your rights if you try to assert (defensively) that their patent is invalid. In other words, you can never sue or even defend yourself against a Facebook lawsuit. For a more balanced approach to patents, see the GPL, Mozilla Public License, or Apache 2.0 License…

This is a common misinterpretation of this clause. There's been a lot of discussion at length here: https://news.ycombinator.com/item?id=8985722

I read that discussion. The patent grant is very asymmetrical. Why should an entity using React be vulnerable to being sued by Facebook for unrelated patents and be unable to challenge those patents?

Re: Ember's Glimmer Engine

#88

Post by simplify »

davexunit wrote: post #37

>building virtual DOM nodes for static areas of your markup that will never change for every change requires many more allocations and increases GC pressure. I'm not familiar with Ember, but why not just store the constant value in a variable to solve this problem? For example, in MithrilJS, you write templates in plain JavaScript, so I just stash large, static parts of the tree in variables and only rebuild vdom nod…

Could you provide an example?

Re: Ember's Glimmer Engine

#89

Post by msane »

mixonic wrote: post #4

Glimmer is a revolutionary improvement in Ember's rendering performance. I'm incredibly excited by the progress and promise being realized in Tom and Yehuda's PR. For more context, here are a few quick slides from the EmberConf keynote: http://f.cl.ly/items/0t031v2Z3y001V1N0F3N/Virtual%20DOM.pdf They, and the PR, tell the whole story about what is happening in the dbmonster demo. We expect this work to land in Ember…

I needed improvements in Ember's rendering performance a year ago, back when performance improvements were already behind schedule.

A situation which still remains in production Ember today: http://youtu.be/z5e7kWSHWTg?t=2m42s

It's too little too late for me. I wouldn't want to touch anything Ember or anything from the authors.

Post reply on HN