Nowadays we expect our compilers to make coffee for us.
That's the kind of conceptual leap computing has made a few times over history - at first the idea of having the computer itself compile your program from a textual form to machine instructions ("auto-coding") was novel and complex. That still takes engineering and design, but the order of magnitude goes down, allowing complexity to bottleneck elsewhere. We can say, "aha, but OCR exists, GPT exists" and pursue a completely different way of presenting many of those features, where you leverage a higher grade of computing power to make the architectural line between the presentation layer and the database extremely short and weighted towards "user in control of their data and presentation". So we added a longer pipeline with more things to configure, over and over.īut - the computing environment is also different now.
screen reading.the development model lacks the abstraction to do layout.and so on. Well, the way in which we got there is in adding more features to the "obvious" answer: all any given site necessarily has to do, to have the same presentation as today, is place pixels on the screen, change the pixels when the user clicks or types things, and persist data somewhere as the user does things.Įxcept.there's no model of precisely how text is handled or how to re-encode it for e.g.
0 kommentar(er)
