From a development efficiency perspective, Famous is not as good as Angular or React. From a rendering perspective, it's not as good as three.js. It's not yet a leading tool. Jack of all trades, master of none. Maybe it will make more sense when VR platforms become mainstream.
Famous Engine – JavaScript library for animations and interfaces
41–50 of 90 posts
Re: Famous Engine – JavaScript library for animations and interfaces
#42I like their new branding and docs. It looks really easy to get up and running, but the basic "hello world" isn't working for me.. npm install -g famous-cli && famous init my-first-project && cd my-first-project && famous project deploy ..and nothing happens. Did I miss something obvious? Also, I'm curious: are there any big companies using famo.us? Are there any non-trivial famo.us applications that we can look at?
oooo... my first chance to add something to Hacker news :D So... the deploy will produce a snippet that is missing the close div
it give you something like this:
" rel="nofollow">https://assets-te.famo.us/embed/embed.js">
add this:
Does this mean I'll get accepted to YC ? (cue Eddie Murphy laugh)
Re: Famous Engine – JavaScript library for animations and interfaces
#43I like their new branding and docs. It looks really easy to get up and running, but the basic "hello world" isn't working for me.. npm install -g famous-cli && famous init my-first-project && cd my-first-project && famous project deploy ..and nothing happens. Did I miss something obvious? Also, I'm curious: are there any big companies using famo.us? Are there any non-trivial famo.us applications that we can look at?
oooo... my first chance to add something to Hacker news :D So... the deploy will produce a snippet that is missing the close div it give you something like this: " rel="nofollow">https://assets-te.famo.us/embed/embed.js"> add this: Does this mean I'll get accepted to YC ? (cue Eddie Murphy laugh)
Re: Famous Engine – JavaScript library for animations and interfaces
#44From a development efficiency perspective, Famous is not as good as Angular or React. From a rendering perspective, it's not as good as three.js. It's not yet a leading tool. Jack of all trades, master of none. Maybe it will make more sense when VR platforms become mainstream.
How much time have you spent with the new release?
Re: Famous Engine – JavaScript library for animations and interfaces
#45I tried to build a website with the "old" famo.us, but it was slow going, once you'd got past the initial setup. You're on your own for widgets!
Also, "famous" or "famo.us" is a BAD name. Sorry, but you can't google for help or tutorials. Google for "famous websites" or "famous tutorials", see what you get. :-/
slow going.
Re: Famous Engine – JavaScript library for animations and interfaces
#46From a development efficiency perspective, Famous is not as good as Angular or React. From a rendering perspective, it's not as good as three.js. It's not yet a leading tool. Jack of all trades, master of none. Maybe it will make more sense when VR platforms become mainstream.
What was released today was a rewrite of the Famous core engine, so you can't really compare it to Angular or React. Three.js is a far better comparison, though the two have different specialties since Famous isn't trying to be pure WebGL.
The Famous team is working on a framework that will interface with their core engine, making things far cleaner at the application level while facilitating less painful integration. Comparing that to various client-side frameworks will definitely make sense.
Re: Famous Engine – JavaScript library for animations and interfaces
#47I tried to build a website with the "old" famo.us, but it was slow going, once you'd got past the initial setup. You're on your own for widgets! Also, "famous" or "famo.us" is a BAD name. Sorry, but you can't google for help or tutorials. Google for "famous websites" or "famous tutorials", see what you get. :-/ slow going.
Famous Engine is a complete rewrite.
0.3 was doing a lot of unnecessary matrix multiplications on a frame by frame basis. It also produced a lot of garbage, resulting into a frame drop every time the GC ran.
Famous Engine produces basically no garbage at all. It has an event based system for updating transforms.
I apologize for your bad experience with "old" famous, but please keep in mind that we started from scratch.
(For disclosure I am an employee of famous)
Re: Famous Engine – JavaScript library for animations and interfaces
#48Are there any examples of products that use the famous framework in production? The lack of case study examples on their website worries me a little.
They regularly spotlight apps on their mailing list[1]. For example: - World Cup App Spotlight[2] - InkaBinka[3] (Only the mobile apps?) [1]: http://us5.campaign-archive2.com/home/?u=4656ba2b0a364690c85... [2]: http://wc.complex.com/ [3]: http://inkabinka.com/
Those two examples are really poor, the usability is terrible in both cases, and the effects are not impressive enough to be worth giving up core features like zoom and copy / paste.
Re: Famous Engine – JavaScript library for animations and interfaces
#49Why does this look like Three.JS code? It seems to have very similar capabilities (although Famo.us seems to have less features) and even the code seems to be familiar to me as a ThreeJS guy. Also I'd argue that ThreeJS can make for better looking results: https://clara.io/view/193070f2-e8af-4afc-a531-9d82338b5288
Code that deals with 3D space tends to look similar. Design patterns that work in such contexts tend to be common sense.
Three.js can make far better looking results currently because it's a full-fledged, mature 3D engine. Famous isn't designed to compete with that. It's really intended to sort of merge DOM and 3D content so you can use both in a unified manner.
Also, trashing someone else's product while plugging your own in the same breath is simply poor taste.
Re: Famous Engine – JavaScript library for animations and interfaces
#50I tried to build a website with the "old" famo.us, but it was slow going, once you'd got past the initial setup. You're on your own for widgets! Also, "famous" or "famo.us" is a BAD name. Sorry, but you can't google for help or tutorials. Google for "famous websites" or "famous tutorials", see what you get. :-/ slow going.
I did some work with 'old' famo.us, and boy was it slow going. Then again, at the time I was relatively new to javascipt, so understanding scope, callbacks and such was hard at the time.
Now its popping up again. Time to take it for another run. The problem in the past was a small/inactive/detached community imo, if there was an active community behind it, it would be amazing.
Also, the famo.us devs seem to expect a lot of community stuff to be happening in or around their offices, which is unfair to us overseas guys who can't go to a famo.us demo day in their office.