Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

and (2020)

danq.me

Post reply on HN
Print view View original

71–80 of 191 posts

Re: <Blink> and <Marquee> (2020)

#71

Post by zambal »

donatj wrote: post #21

I was there, 3,000 years ago. I remember fights over whether or not navigation in frames was bad practice. Not iframes, frames. Who here remembers frames? I remember using HTTP 204 before AJAX to send messages to the server without reloading the page. I remember building... image maps[1]... professionally in the early 2000. I remember spending multiple days drawing the borders of States on a map of the country in Dre…

Don't know if it was intentional, but your ramble reminded me of the lyrics of Losing my edge by LCD Soundsystem. However, as someone who also experienced most of this stuff, it was a fun read either way :)

Re: <Blink> and <Marquee> (2020)

#72

Post by skerit »

jameslk wrote: post #50
donatj wrote: post #21

I was there, 3,000 years ago. I remember fights over whether or not navigation in frames was bad practice. Not iframes, frames. Who here remembers frames? I remember using HTTP 204 before AJAX to send messages to the server without reloading the page. I remember building... image maps[1]... professionally in the early 2000. I remember spending multiple days drawing the borders of States on a map of the country in Dre…

I remember meticulously using the photoshop slice tool To export gifs meant to be positioned perfectly in HTML tables For designs suited best for 800x600 All those moments lost in time, like tears in the rain

> I remember meticulously using the photoshop slice tool

I made so many newsletters using that tool back in 2009. I remember a new designer was appalled I used it, and did not write the HTML code manually... 70% of our receivers were using Outlook and the horrible Word-based HTML renderer. I'm not writing anything manual for that piece of crap.

Re: <Blink> and <Marquee> (2020)

#73

Post by Timwi »

donatj wrote: post #21

I was there, 3,000 years ago. I remember fights over whether or not navigation in frames was bad practice. Not iframes, frames. Who here remembers frames? I remember using HTTP 204 before AJAX to send messages to the server without reloading the page. I remember building... image maps[1]... professionally in the early 2000. I remember spending multiple days drawing the borders of States on a map of the country in Dre…

I developed web software with frames and I thought it was perfectly fine. To this day I still don't understand the issue with frames. People sometimes mention accessibility for screen readers, but nothing more specific than that, so I still don't know what the actual problem is.

Re: <Blink> and <Marquee> (2020)

#74

Post by ripdog »

bornfreddy wrote: post #62
flomo wrote: post #41

Earlier quoted context omitted.

Root for the illegal Google monopoly then, because that's what Mozilla says they need to survive. (It's over soon.)

I assume you were being sarcastic? I see it the other way around - the sooner Mozilla gets off the drugs^WGoogle's money the better the chance we get a proper competitor to Chrome.

Um, so, how are Mozilla supposed to get the hundreds of millions of dollars a year it costs to pay engineers to maintain an evergreen browser without Google's funding?

Re: <Blink> and <Marquee> (2020)

#75

Post by ChrisMarshallNY »

I was a Master Navigator of the Meat Mysterious[0].

My magnum opus was a Flash site, that looked like a blank black page, and revealed the page structure, in a fuzzed circle, as you moused around. It was, literally, a flashlight in a dark room interface.

You could probably do the same, these days, with CSS. Back then, you needed Flash.

The space must flow…

[0] https://en.m.wikipedia.org/wiki/Mystery_meat_navigation

Re: <Blink> and <Marquee> (2020)

#76

Post by xnx »

Timwi wrote: post #73
donatj wrote: post #21

I was there, 3,000 years ago. I remember fights over whether or not navigation in frames was bad practice. Not iframes, frames. Who here remembers frames? I remember using HTTP 204 before AJAX to send messages to the server without reloading the page. I remember building... image maps[1]... professionally in the early 2000. I remember spending multiple days drawing the borders of States on a map of the country in Dre…

I developed web software with frames and I thought it was perfectly fine. To this day I still don't understand the issue with frames. People sometimes mention accessibility for screen readers, but nothing more specific than that, so I still don't know what the actual problem is.

All content on the web should have a unique, linkable, URL. Frameset breaks that.

Re: <Blink> and <Marquee> (2020)

#77

Post by xnx »

42droids wrote: post #37
donatj wrote: post #21

I was there, 3,000 years ago. I remember fights over whether or not navigation in frames was bad practice. Not iframes, frames. Who here remembers frames? I remember using HTTP 204 before AJAX to send messages to the server without reloading the page. I remember building... image maps[1]... professionally in the early 2000. I remember spending multiple days drawing the borders of States on a map of the country in Dre…

Started in 1998 with front page.

Fancy! Not even Front Page Express first?

Re: <Blink> and <Marquee> (2020)

#78

Post by Theodores »

One reason people hate these elements is that they were overused.

However, with that over use, people were giving HTML a go. For someone new to writing HTML, it was very rewarding to be able to use or . These were the gateway drugs of the HTML world, and, anyone that used these elements would eventually learn not to, or maybe not, if it was their mySpace page.

It is easy to hate on the and elements, much like how every snobbish graphic designer can chortle about stupid people using Comic Sans, however, all of these no-no's had great utility in giving people confidence to give things a go.

Re: <Blink> and <Marquee> (2020)

#80

Post by xnx »

moralestapia wrote: post #8

Never got the hate to these. I think some people just want to feel important by diminishing things they see others diminishing, makes up from not having thoughts of one's own. This applies to everything, not just HTML obv.

As others have said: scrolling text is harder to read than non-scrolling text. Scrolling text is useful in the real world when space is limited. On the web, there is no space limit, so almost no reason for scrolling text.
Post reply on HN