A picture of Edsger Dijkstra with a concerned face and the following text on top: How software engineers look at your code when you solve the problem using two tables — instead of using the Maxwell-Ross-Karmakar algorithm, which is marginally optimal in ordered sets bijectable to the exponential curve
you are viewing a single comment's thread
view the rest of the comments
[–] 18 points 1 month ago* (last edited 1 month ago) (3 children)

software engineers met the table¹ in web design and never looked back. does a table "mean" tfoot and all (arranged at top)? thead, that sorts(, by server link without javascript)? a "table" in the web means all sorts of sorty things (i mean even "drag and drop" first should meet with server links that move a row up and down — maybe reveal the "buttons" through tap+hold on the row in CSS, and so on) and offset things, and paginated things, by navigable server links, even hide and filter fields by URI! and the two tables nested for layout, oy vey! so many ways with all that engineering the web fell to the broken manual✨️🤷🏾‍♂️✨️

¹ (for layout) https://www.w3.org/TR/web-sustainability-guidelines/#progressive-enhancement

  • source
  • hideshow 3 child comments