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

FOAM: New JavaScript Framework by Google Engineers

github.com

Post reply on HN
Print view View original

71–80 of 115 posts

Re: FOAM: New JavaScript Framework by Google Engineers

#71

Post by justthistime_ »

hosay123 wrote: post #46
Rifu wrote: post #2

Doesn't seem to actually be by Google. Perhaps the title could be changed to "by a Google Engineer"?

They probably have rights to the project under the respective contracts they have with the employees. That aside, having " by ((Google(|rs))| )" in the title has generally been a reliable filter for projects that do not stand on their own merit, and this one seems to be no exception.

Exactly.

Everyone should ask himself/herself "would this be newsworthy if they didn't name-drop Google?".

Re: FOAM: New JavaScript Framework by Google Engineers

#72

Post by Demiurge »

miralabs wrote: post #49
thomasfl wrote: post #10

It's about time more people starts using ES6 class constructors instead of rolling their class definition hack. This is how it's done in the calculator demo: CLASS({ name: 'Calc' With babeljs you can use ES6 syntax like this: class Calc { }

Crockford talks about the bad features added to ES6, one of them class which he said is most requested by Java developers programming javascript.At the end of the talk he show way how to move out of classes/new in javascript https://www.youtube.com/watch?v=PSGEjv3Tqo0&feature=youtu.be...

Can you give a short gist of why they're bad and why should one move out of classes/new? What is the alternative?

Re: FOAM: New JavaScript Framework by Google Engineers

#74

Post by davej »

Demiurge wrote: post #72
miralabs wrote: post #49

Earlier quoted context omitted.

Crockford talks about the bad features added to ES6, one of them class which he said is most requested by Java developers programming javascript.At the end of the talk he show way how to move out of classes/new in javascript https://www.youtube.com/watch?v=PSGEjv3Tqo0&feature=youtu.be...

Can you give a short gist of why they're bad and why should one move out of classes/new? What is the alternative?

From the video:

    function constructor(spec) {
      let {member} = spec,
          {other}  = other_constructor(spec),
          method   = function () {
            // accesses member, other, method, spec
          };

      return Object.freeze({
          method,
          other,
      });
    }

Re: FOAM: New JavaScript Framework by Google Engineers

#75

Post by seanmcdirmid »

eropple wrote: post #70
seanmcdirmid wrote: post #28

Earlier quoted context omitted.

Rendering code is easy to express as pure functions...that is mostly how OpenGL and DirectX work, after all. React doesn't help very much with the state of your application (nor is it meant to). That being said, being able to treat the DOM as something to be rendered efficiently in immediate mode is quite useful.

OpenGL is a big ol' box of state in almost everything it does. I'm not sure how you get pure functions out of that.

Immediate shader mode is fairly stateless, pixel and vertex shaders are as functional as one can get. Let's not talk about the fixed function APIs that no one uses anymore.

Re: FOAM: New JavaScript Framework by Google Engineers

#76

Post by ramblerman »

venomsnake wrote: post #32

> FOAM is a full-stack Reactive MVC Meta-Programming framework. 5 years ago I would have thought that this would have been the title of the tech section of Onion article ...

And hackernews wasn't full of snarky one liners. Did you even read further than that before you just had to get your comedy 'out there'?

Re: FOAM: New JavaScript Framework by Google Engineers

#78

Post by eropple »

seanmcdirmid wrote: post #75
eropple wrote: post #70

Earlier quoted context omitted.

OpenGL is a big ol' box of state in almost everything it does. I'm not sure how you get pure functions out of that.

Immediate shader mode is fairly stateless, pixel and vertex shaders are as functional as one can get. Let's not talk about the fixed function APIs that no one uses anymore.

I'm not sure what you mean by "immediate shader mode". Even direct state access mode is tweaking knobs in a state machine that can have very strange side effects if you don't re-set the state every time (and that's antithetical to pure functional programming). When not using DSA--I mean, just grep for "bind" in any OpenGL codebase...

Re: FOAM: New JavaScript Framework by Google Engineers

#80

Post by venomsnake »

ramblerman wrote: post #76
venomsnake wrote: post #32

> FOAM is a full-stack Reactive MVC Meta-Programming framework. 5 years ago I would have thought that this would have been the title of the tech section of Onion article ...

And hackernews wasn't full of snarky one liners. Did you even read further than that before you just had to get your comedy 'out there'?

I did. After reading the whole page I was not able to determine what it does ...

Edit: Also 5 years ago HN was even fuller with snarky one liners and eyebrow dismissals.

Post reply on HN