Live data from Hacker News

Netflix Releases Falcor Developer Preview

techblog.netflix.com

41–50 of 53 posts

Re: Netflix Releases Falcor Developer Preview

#41

I have been following the falcor announcements, presentations and discussions for a few months. I am really impressed at what a good job the Netflix team has done with introducing the json graph concepts, I've learned a lot it regardless of falcor. Kudos Netflix! I really like the concepts and client/server model. If it is performant, it will be fun to see persistent videogame worlds written through falcor. To that e…

how have you been following this? I'd like to look at the json graph concepts you're talking about and having the discussion to go along with it would be very helpful.

Re: Netflix Releases Falcor Developer Preview

#42
post #24

IMO, the name is to close to that of the Falcon (Python) web framework. http://falconframework.org/

I disagree, though maybe I could see your point if you are unfamiliar with The Never-ending Story. Even then, they are in different spaces so a mental name collision seems unlikely.

[deleted]

Re: Netflix Releases Falcor Developer Preview

#44
This is really interesting and welcome contribution in an important space. Three features that would make it compelling:

1. Offline. Making the local datastore as "invisible" as the memory cache and the cloud - keeping everything in sync under the hood. 2. Push. Notifying clients when changes occur. 3. Diff. Efficiently handling changes in larger values.

I realise none of these are central to the challenge they faced, and congratulate them on an elegant solution for their situation.

Re: Netflix Releases Falcor Developer Preview

#45
I think Falcor is conceptually interesting, but after reading some of the documentation and project code, I don't want to use it (at this point).

The library bills itself as "middleware", but it looks more like an application framework. I don't see how this would cleanly fit with other application frameworks, as it appears that you have to use Falcor models, routers, and datasources.

The project's code is concerning in a few ways: it's a large codebase, it reads more like C++ than JavaScript, and there's not enough comments. In my experience, successful JavaScript libraries are: small, use JS conventions, and have well-documented source code.

It's great that they are releasing open-source software, though. I hope that this project evolves into something that I want to use.

Re: Netflix Releases Falcor Developer Preview

#46
post #45

I think Falcor is conceptually interesting, but after reading some of the documentation and project code, I don't want to use it (at this point). The library bills itself as "middleware", but it looks more like an application framework. I don't see how this would cleanly fit with other application frameworks, as it appears that you have to use Falcor models, routers, and datasources. The project's code is concerning…

What's an example of the C++ conventions you're referring to? I'm looking at the source now trying to identify them. I don't see them. Looks javascripty to me.

Re: Netflix Releases Falcor Developer Preview

#47

I really admire Netflix's ability to put together developer documentation for their open source projects. I think it reflects well on their engineering culture. I was similarly impressed when I was reading the documentation for Hystrix, which seems to share some functionality with Falcor, like request batching and caching. The path syntax is very readable and obviously plays to JavaScripts strengths as a dynamic lang…

I'm yet to come across a data layer for JS that plays nicely with Flow. Even Facebook's Flux struggles with it. I've been trying to work on my own implementation of the "Flux" architecture (unidirectional data flow), but I'm curious whether you know any decent "model" layers that work nicely in the weird statically-typed "JS" world?

Re: Netflix Releases Falcor Developer Preview

#49

This is really interesting and welcome contribution in an important space. Three features that would make it compelling: 1. Offline. Making the local datastore as "invisible" as the memory cache and the cloud - keeping everything in sync under the hood. 2. Push. Notifying clients when changes occur. 3. Diff. Efficiently handling changes in larger values. I realise none of these are central to the challenge they faced…

yes it has offline :) They're working on the roadmap for Push

Re: Netflix Releases Falcor Developer Preview

#50

I have been following the falcor announcements, presentations and discussions for a few months. I am really impressed at what a good job the Netflix team has done with introducing the json graph concepts, I've learned a lot it regardless of falcor. Kudos Netflix! I really like the concepts and client/server model. If it is performant, it will be fun to see persistent videogame worlds written through falcor. To that e…

iirc, falcor maintains an LRU cache, so unused data keeps getting flushed out of memory.

LRU = Least recently used.
Post reply on HN