I remember seeing a co-worker stuck on trying to debug Netscape showing a blank page. When I looked at it, it wasn’t showing a blank page per se, it was just taking over a minute to render tables nested twelve deep. I deleted exactly half of them with no change to the layout or functionality, and it immediately started rendering in under a second.

Six nesting levels for tables? Cool, what were you making?

That's a fun trick, but please consider adding ARIA roles (e.g. role="presentation" to <table>, role="heading" aria-level="[number]" to the <font> elements used for headings) to make your site understandable by screen readers.

Your logo gets cut off in Firefox https://i.ibb.co/kbj5vw7/image.png

> Why not!

Responsive layout would be the biggest reason (mobile for one, but also a wider range of PC monitor aspect ratios these days than the 4:3 that was standard back then), probably followed by conflating the exact layout details with the content, and a separation of concerns / ease of being able to move things around.

I mean, it's a perfectly viable thing if these are not requirements and preferences that you and your system have. But it's pretty rare these days that an app or site can say "yeah, none of those matter to me the least bit".

wasn't it Fireworks that sliced the image originally. you'd then be able to open that export into Dreamworks for additional work. I didn't do that kind of design very long. Did Dreamworks get updated to allow the slicing directly bypassing Fireworks?

Apparently Outlook (the actual one, not the recent pretender) still uses some ancient WordHTML version as the renderer, so there isn’t much choice.

Oh yeah, recently I had to update a newsletter design like that and older versions of outlook still didn’t render properly.

You jest, but it took forever to add somewhat intuitive layout mechanism to css which allowed you to do what could be done easily with html tables. Vertically centering a div inside another was really hard, and very few people understood the techniques you would use, instead of blindly copying them.

It was beyond irony that the recommended solution was to tell the browser to render your divs as a table.

CSS was a mistake? JavaScript was a mistake, specifically JavaScript frameworks.

Y Combinator funded one such company, MarkupWand.[1] A friend is one of the co-founders.

1. https://www.ycombinator.com/companies/markupwand

The author said he had the assets and gave them to Claude. It would be obvious if he had one large image for all the planets instead of individual ones.