5 ms·

> That scores within 7% of Readability’s output on a selection of its own test cases "on a selection of" its own test cases = lol > Fathom is a data-flow lang

> That scores within 7% of Readability’s output on a selection of its own test cases "on a selection of" its own test cases = lol > Fathom is a data-flow language like Prolog, so data conveniently “turns up” when there are applicable rules that haven’t yet seen it Why are you trying to explain the concept of declarative programming without just telling people about declarative programming? Just because it's not common in a scene doesn't make it some proprietary concept you've just introduced there. > The best part is that Fathom rulesets are data That's actually kinda nice > In 70 lines, Insert that comic about 'just a few lines' masking the function calls that actually don't 'replace' a system, just change where work is being done when flexibility is not needed

TeMPOraL 9y ago
> Insert that comic about 'just a few lines' masking the function calls that actually don't 'replace' a system, just change where work is being done when flexibility is not needed Do you have link for that comic? I think haven't seen it. The concept you describe is very important though - abstractions like that are usually about moving complexity around (compare Turing tarpit - all Turing-complete languages are in principle equivalent; the difference is in their distribution of complexity along the axis of programs you want to write).
grincho 9y ago
You might prefer the more technical introduction at https://mozilla.github.io/fathom/intro.html#specific-areas-we-address https://mozilla.github.io/fathom/intro.html#specific-areas-w.... It talks about Fathom in terms of declarativeness. > "on a selection of" One has to start somewhere! At this early stage, my aim is to demonstrate that Fathom has value for simplifying the implementation of recognizers, not to claim a polished, production-ready Readability alternative. Though, frankly, getting to the latter would be a fun project for someone: just write more features (in the ML sense), and add more tuning data. There are lots of low-hanging TODOs in the code around https://github.com/mozilla/fathom/blob/master/examples/readability.js#L52 https://github.com/mozilla/fathom/blob/master/examples/reada....

TeMPOraL 9y ago

> Insert that comic about 'just a few lines' masking the function calls that actually don't 'replace' a system, just change where work is being done when flexibility is not needed Do you have link for that comic? I think haven't seen it. The concept you describe is very important though - abstractions like that are usually about moving complexity around (compare Turing tarpit - all Turing-complete languages are in principle equivalent; the difference is in their distribution of complexity along the axis of programs you want to write).

grincho 9y ago

You might prefer the more technical introduction at https://mozilla.github.io/fathom/intro.html#specific-areas-we-address https://mozilla.github.io/fathom/intro.html#specific-areas-w.... It talks about Fathom in terms of declarativeness. > "on a selection of" One has to start somewhere! At this early stage, my aim is to demonstrate that Fathom has value for simplifying the implementation of recognizers, not to claim a polished, production-ready Readability alternative. Though, frankly, getting to the latter would be a fun project for someone: just write more features (in the ML sense), and add more tuning data. There are lots of low-hanging TODOs in the code around https://github.com/mozilla/fathom/blob/master/examples/readability.js#L52 https://github.com/mozilla/fathom/blob/master/examples/reada....