2 ms·
It matches TFA, but I think 'Framework' in that capitalisation (incorrectly) implies it's about Framework (https://frame.work https://frame.work) the company.
by OJFord 4y ago
It matches TFA, but I think 'Framework' in that capitalisation (incorrectly) implies it's about Framework (https://frame.work https://frame.work) the company.
I think quotes - 'framework' - would be better, both here and in the OP; we can fix one of those.
- a4isms 4y agoI'm so old, I thought of the productivity suite from the 1980s: https://en.wikipedia.org/wiki/Framework_(office_suite) https://en.wikipedia.org/wiki/Framework_(office_suite) I still think about that suite, because it had a certain kind of elegance: Everything was frame, and therefore text documents and spreadsheets were frames, and you could embed a frame in a document, which correctly implies you could put a spreadsheet in a text document. But the cells in a spreadsheet were frames, and therefore you could make a hierarchal spreadsheet, or put a text document in a spreadsheet's cells, and so on. It had a "frames all the way down" philosophy that appealed to me, although the implementation was hobbled by the (to us) obvious limitations of the technology of its time. From the wikipedia link: The spreadsheet program was superior in its day, offering true 3D capability, where spreadsheets could form an outline which can be "opened" to reveal a separate spreadsheet, as well as other frame types — a feat of sheer convenient function never again seen and further enhanced in later versions. Framework's built-in interpreter, the FRED (Frame Editor) computer language, was based on Lisp eval function. It can reference all frames and types across the product and can sense and perform all user interface operations.
- heavyset_go 4y agoI had the same misconception. Updating the title would fix the potential double meaning, in my opinion.