11–20 of 23 posts
He's talking about basic arithmetic. Sums. Averages. (Front end design ought to have more math behind the scenes, like a constraint solver, and less arithmetic visible to the web designer.)
He's talking about basic arithmetic. Sums. Averages. (Front end design ought to have more math behind the scenes, like a constraint solver, and less arithmetic visible to the web designer.)
How would one express those constraints? I think it's more efficient to let a human designer figure out some approximation of decent design and usability.
It took decades to get CAD GUIs right, but now they're quite good. They solve a far harder problem than web design. Look to them for guidance.
Earlier quoted context omitted.
How would one express those constraints? I think it's more efficient to let a human designer figure out some approximation of decent design and usability.
The way it's done in 2D sketch programs such as the sketch feature of Fusion 360 or Autodesk Inventor. Graphically. I've discussed this before on HN. All the modern CAD systems do this. It took decades to get CAD GUIs right, but now they're quite good. They solve a far harder problem than web design. Look to them for guidance.
He's talking about basic arithmetic. Sums. Averages. (Front end design ought to have more math behind the scenes, like a constraint solver, and less arithmetic visible to the web designer.)
I think we should be emphasizing mathematical knowledge in front-end design and implementation, not trying to hide it under the covers. The better you are at math, the easier it is for you to implement the correct system for the design you want, and the less you have to compromise the design to fit the systems you have at hand.
He's talking about basic arithmetic. Sums. Averages. (Front end design ought to have more math behind the scenes, like a constraint solver, and less arithmetic visible to the web designer.)
2. Once browser creates DOM and CSSOM how does it use this information to create the view that I see?
He's talking about basic arithmetic. Sums. Averages. (Front end design ought to have more math behind the scenes, like a constraint solver, and less arithmetic visible to the web designer.)
At least, the dot graph layout language uses integer programming to lay out it's graphs.
Off topic, but are there any accessible resources to learn: 1. How fonts get rendered? What happens when I present browser with a font file and some utf-8 bytes, how does it convert this into viewable text. 2. Once browser creates DOM and CSSOM how does it use this information to create the view that I see?
https://developers.google.com/web/fundamentals/performance/o...
He's talking about basic arithmetic. Sums. Averages. (Front end design ought to have more math behind the scenes, like a constraint solver, and less arithmetic visible to the web designer.)
How would one express those constraints? I think it's more efficient to let a human designer figure out some approximation of decent design and usability.