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

111–120 of 191 posts

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

#111

Post by bornfreddy »

ripdog wrote: post #74
bornfreddy wrote: post #62

Earlier quoted context omitted.

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?

How did they survive without their funding before they got it? And don't say that web standards are much more complex nowadays - yes, they are, because it is in Google's interest to make them such. Will it hurt? Yes. Will Firefox survive? I hope so. Is it a bad idea? No.

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

#112

Post by Waterluvian »

timpark wrote: post #29

The blink tag was, of course, much hated back in the day, so as an experiment, I took the binary of whatever browser I was using (Netscape, I guess), searched for "blink", and changed it to "blonk". Tada, no more blinking!

I do this kind of thing with the Slack client (a silver lining of Electron apps: it’s dead simple) so that I can kill features I don’t like, such as hiding notifications or stopping the signal that I’m writing a message.

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

#113

Post by roryirvine »

theandrewbailey wrote: post #86
xnx wrote: post #76

Earlier quoted context omitted.

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

That doesn't stop today's dynamically updating pages that also break the back button.

Frames also broke the back button when they were first introduced!

Together with the other early problems - ugly borders, proliferation of scrollbars, and limited browser compatibility - it meant that frames were seen as a usability disaster right from the start.

They never managed to fully shake that reputation even as browsers improved in the later 90s.

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

#114

Post by crabique »

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 WML tag, essentially SPA 20 years before SPA even became a term.

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

#116

Post by mcswell »

I've wondered whether the marquee idea could be behind the UFOs/ UAPs that appear to move extremely fast. Specifically, you line up a bunch of drones that can communicate with each other via directional (or just weak) radio or laser transmissions. Then when a drone on one end of the line receives a radar pulse from an aircraft (etc.), it sends back a stronger pulse than its reflection would be, and simultaneously signals the next drone in line. That drone sends off a radar pulse and signals the next drone in line, etc. The effect, as viewed from the aircraft with the radar, would be a somewhat larger (or more reflective) target moving rapidly. The line of drones would not need to be straight, in which case it could simulate a fast-moving object that suddenly turns.

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

#117

Post by mcswell »

shortrounddev2 wrote: post #107
echelon wrote: post #104

Earlier quoted context omitted.

We should have frozen the web from 2006 - 2010 or so. We had Ajax, lots of modern CSS, but weren't hell-bent on CSSifying and "SPA"-ing everything. Web standards hadn't yet jumped the shark. It's also before Steve Jobs murdered Flash. Killing Flash was one of the biggest mistakes we've made. The modern HTML/CSS/JS stack can't replicate how simple and functional it was. We're easily dealing with 100x the complexity no…

I agree. Personally I think we'd be better off without social media sites or smart phones

Punch cards. We need to go back to punch cards.

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

#118

Post by skeeter2020 »

trallnag wrote: post #94
shawn_w wrote: post #40

Earlier quoted context omitted.

I don't know how people can use anything else, especially now that Chrome doesn't support ad blockers.

It still supports stripped down as blockers. For the casual user something like ublock lite is probably perfectly fine

if you switch between chrome and FF (say work/home) the difference are glarring though...

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

#120

Post by mcswell »

b800h wrote: post #66
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 was expecting you to tell me that all of these moments will be lost in time, like tears in the rain.

b800h, meet jameslk (see post a few lines above yours)
Post reply on HN