When I came to the realization this isn't satire, another piece of my soul died.
Introducing the Famous Framework
81–90 of 94 posts
Re: Introducing the Famous Framework
#82Earlier quoted context omitted.
This. I can't find a single example of an actual UI you'd build with famo.us on their entire site. How am I supposed to know what makes the framework worth learning if I don't see examples of what it makes possible?
http://famous.org at least shows some code samples, but I agree - it'd be nice to see a real interface, as opposed to an animation. It would also be great to see how Famous isn't a re-skin of MVC with a React-flavored API.
[deleted]
Re: Introducing the Famous Framework
#83The Javascript framework space isn't competitive...it's saturated for the exact same reason that the PHP framework space was saturated.
Javascript and PHP frameworks are all built on top of a language that does everything you need for the web before you even start the framework. Frameworks in both languages are basically an exercise in arranging things according to your personal preferences...and people have a wide range of preferences.
Re: Introducing the Famous Framework
#84Earlier quoted context omitted.
Last time I checked? Mercury or Om. But neither of them comes even close to the level of hype famous had (back when it was famo.us).
Wow, things move really fast in this space. Is "back when" May 2015? The only context I have is the "Didn't you just release Famous in May?" quote from the article.
The original hype was when they were in closed beta, which was way more than a year ago. Internet Archive[0] indicates they started promoting it as early as January 2013.
Things do move fast, but hype doesn't move that fast. The reason I'm cautious is that they were extremely hyped before being able to deliver any actual code developers could use and that in the time since the original announcement, well, all of the past two and a half years happened (e.g. React).
[0]: https://web.archive.org/web/20130715000000*/http://famo.us
EDIT: Here's the January 2013 beta marketing website: https://web.archive.org/web/20130110063331/http://famo.us/
Re: Introducing the Famous Framework
#85A shame they don't even mention Web Components or custom elements, considering that much of what they are addressing in terms of composability and interop with other frameworks is exactly addressed by these standards.
Re: Introducing the Famous Framework
#86Re: Introducing the Famous Framework
#87Re: Introducing the Famous Framework
#88We use dependency injection to match State names to parameters of Behavior functions—the State numberOfStates gets injected into any Behavior function that lists is as a parameter, like function(numberOfStates). We need to have a talk. First, this isn't dependency injection - you're passing in data. These "Behavior" functions may depend on the data, but that doesn't make this a dependency . Oh, I can understand how y…
> These "Behavior" functions may depend on the data, but that doesn't make this a dependency. Would you mind clarifying this distinction as you see it? As far as I can see, x depends on y if and only if y is a dependency of x. This would make the States that Behaviors depend on a 'dependency,' based on your statement above that 'functions ... depend on the data [States].' These State dependencies (if we can agree on…
Because state is data. You operate on data, not depend on it.
My repository depends on a database connection (be it mock or real). It does not depend on what state the tables may be in.
If your function operates on data, it's "passing in data" and not "dependency injection". Hell, otherwise, every function call would involve dependency injection!
Re: Introducing the Famous Framework
#89We use dependency injection to match State names to parameters of Behavior functions—the State numberOfStates gets injected into any Behavior function that lists is as a parameter, like function(numberOfStates). We need to have a talk. First, this isn't dependency injection - you're passing in data. These "Behavior" functions may depend on the data, but that doesn't make this a dependency . Oh, I can understand how y…
Wait, are they seriously trying to say that "function(numberOfStates)" is dependency injection?
I have to reply because I can't edit.
To the down voters:
Function(numberOfStates) is a function call with data being passed in.
Function(stateMachineFactory) is dependency injection.
Re: Introducing the Famous Framework
#90Earlier quoted context omitted.
No. No, it isn't. And even if it were, it's possible to have a useful response beyond a webcomic link that every idiot posts when anything new happens.
That was a joke... but I guess when it comes to front-end frameworks, we can't laugh.
Regurgitated links are not jokes.