News for hackers. Stuff that matters.
Re:Ask HN: Why did famous.js fail? by Kinnard on Monday July 18, 2016 @08:31PM (#12118795)
Why are declarative languages better for UI?
Re:Ask HN: Why did famous.js fail? by flukus on Monday July 18, 2016 @08:48PM (#12118854)
Because it provides I nice separation between the "static" parts of a program, the UI, and the dynamic parts, the data.

The first demo of this on the other hand, has html embedded in javascript strings. A program of any complexity written like this would quickly turn into a big ball of mud.

Re:Ask HN: Why did famous.js fail? by Kinnard on Monday July 18, 2016 @09:18PM (#12118941)
I'm somewhat skeptical of this separation of concerns
Re:Ask HN: Why did famous.js fail? by flukus on Monday July 18, 2016 @11:34PM (#12119397)
I'd encourage you to try it out:

http://jsfiddle.net/rniemeyer/LkqTU/

Re:Ask HN: Why did famous.js fail? by iamleppert on Monday July 18, 2016 @10:24PM (#12119147)
It's possible to turn any codebase into a big ball of mud. Declarative languages are just a tool, like object oriented languages are.

And arguably, if you choose a language based upon its ability to help you define what is "dynamic" vs. "static" you've made some mistakes.

Re:Ask HN: Why did famous.js fail? by Kinnard on Monday July 18, 2016 @10:34PM (#12119178)
>"And arguably, if you choose a language based upon its ability to help you define what is "dynamic" vs. "static" you've made some mistakes."

Please elaborate.

Re:Ask HN: Why did famous.js fail? by yrezgui on Monday July 18, 2016 @08:43PM (#12118839)
They're easier to read and code. Check out XAML for C#, it's dead simple. But one of their main problem is they advertised for too long (I remember waiting for ages) and we didn't get the 60 fps. It wasn't as fast as announced and painful to integrate.
Re:Ask HN: Why did famous.js fail? by flukus on Monday July 18, 2016 @08:49PM (#12118858)
I'd say check out knockoutjs instead, way simpler than xaml.