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

Star Wars opening crawl from 1977 in HTML/CSS/JS

codepen.io

Post reply on HN
Print view View original

21–30 of 68 posts

Re: Star Wars opening crawl from 1977 in HTML/CSS/JS

#21

Post by ghayes »

pyalot2 wrote: post #16
TimPietrusky wrote: post #9

Earlier quoted context omitted.

So what do you suggest I should change? Thanks in advance.

Well in CSS you can't do anything about it, that's just how the browser works. If you'd be doing WebGL you can do some things like using square power of two textures and enabling mipmapping and if available anisotropic filtering. You can also do things like using signed distance field fonts or draw fonts by rasterizing (in the fragment shader) the bezier curves, which can be made to nicely anti-alias (using standard…

Is this to say that CSS 3D transformations on text are bound to be aliased [in similar circumstances]? Is there a suggestion to the spec such as a "mipmap hint" that could (one day) be added to reduce this flaw without the need for other technologies?

Re: Star Wars opening crawl from 1977 in HTML/CSS/JS

#22

Post by jacquesm »

goggles99 wrote: post #13

Cool, but sadly to me this is almost a parody of how modern web dev innovation HTML5/JS/CSS are so far behind the technology that actually exists in the world today (this was originally created in 1977). Web standards are good, but much faster and be far more "open" and expandable. One suggestion. Don't just create a standard for (monopoly) ECMA Script, instead - create a standard for a VM that other languages can co…

> Don't just create a standard for (monopoly) ECMA Script, instead - create a standard for a VM that other languages can compile bytecode to. Create an API in this VM for graphics, video, audio, ETC.

Please no. That's the opposite of where we should be going. Less executable code on the client, more powerful markup.

JavaScript was a huge mistake that we will likely have to live with for decades, let's not compound it.

Re: Star Wars opening crawl from 1977 in HTML/CSS/JS

#23

Post by f055 »

goggles99 wrote: post #13

Cool, but sadly to me this is almost a parody of how modern web dev innovation HTML5/JS/CSS are so far behind the technology that actually exists in the world today (this was originally created in 1977). Web standards are good, but much faster and be far more "open" and expandable. One suggestion. Don't just create a standard for (monopoly) ECMA Script, instead - create a standard for a VM that other languages can co…

"this is almost a parody of how modern web dev innovation HTML5/JS/CSS are so far behind the technology that actually exists in the world today (this was originally created in 1977)"

That's a weird opinion. The original was analog, created by several people and shoot carefully in specific conditions. This HTML version was made by a guy in his bedroom in a fraction of a time and is sharable, editable and can be viewed on many devices, including mobile, instead of just a movie theatre like the original. For me this is innovation across the board (not only in web standards, but technology overall)

Re: Star Wars opening crawl from 1977 in HTML/CSS/JS

#24

Post by icebraining »

goggles99 wrote: post #13

Cool, but sadly to me this is almost a parody of how modern web dev innovation HTML5/JS/CSS are so far behind the technology that actually exists in the world today (this was originally created in 1977). Web standards are good, but much faster and be far more "open" and expandable. One suggestion. Don't just create a standard for (monopoly) ECMA Script, instead - create a standard for a VM that other languages can co…

One suggestion. Don't just create a standard for (monopoly) ECMA Script, instead - create a standard for a VM that other languages can compile bytecode to. Create an API in this VM for graphics, video, audio, ETC. This may be self defeating for these clowns, because JavaScript/CSS/HTML may be decimated in a decade if they actually did this, but hey... One can hope.

How would that bytecode be any less of a "monopoly" than ECMA Script is now?

Web standards may be "far behind" in what they can do compared to native code, but their are far, far, far ahead in terms of giving some control back to the user, whether it's in terms of enabling browser extensions, letting content be viewed without running arbitrary code, doing presentation transformations (e.g. Readability), well defined semantics for sharing content (links), etc.

Your suggestion would grant some more power to developers, at the expense of users. So thanks, but no thanks.

Re: Star Wars opening crawl from 1977 in HTML/CSS/JS

#26

Post by mercer »

TimPietrusky wrote: post #12
jasonkester wrote: post #11

Gotta preload that audio. Even 100ms of lag between the logo showing up and the music starting is noticeable. Jarring even for (presumably) most of us, who have seen that opening crawl dozens, hundreds, or possibly for children of the 70s who went on to own laserdisc players in the 80s, thousands of times. In any other context, you could safely pull off not preloading. But this example is just too ingrained into peop…

Yeah I know and it's freaking me out. I already use the attribute preload="auto" of the -element, but it's not enough. Do you know any better ways to preload it?

I'm assuming there's an event for when the audio is loaded... maybe hook up the animation to that?

Re: Star Wars opening crawl from 1977 in HTML/CSS/JS

#27

Post by lookingsideways »

pyalot2 wrote: post #7

Ah my eyes, the aliasing. If anybody's interested why there's aliasing it's important to know how CSS transforms work. If you transform, the browser lifts the transformed rectangle into its own layer and renders its content to a texture. Then, later, it is composited with the page by blitting that texture with whatever transformation was applied. So CSS transforms are an application of texturing. And in texturing wha…

Are you able to upload a screenshot of the aliasing problem somewhere?

Running on a retina MBP, both Safari and Chrome render the text pin-sharp with no noticeable aliasing.

Re: Star Wars opening crawl from 1977 in HTML/CSS/JS

#29

Post by pyalot2 »

ghayes wrote: post #21
pyalot2 wrote: post #16

Earlier quoted context omitted.

Well in CSS you can't do anything about it, that's just how the browser works. If you'd be doing WebGL you can do some things like using square power of two textures and enabling mipmapping and if available anisotropic filtering. You can also do things like using signed distance field fonts or draw fonts by rasterizing (in the fragment shader) the bezier curves, which can be made to nicely anti-alias (using standard…

Is this to say that CSS 3D transformations on text are bound to be aliased [in similar circumstances]? Is there a suggestion to the spec such as a "mipmap hint" that could (one day) be added to reduce this flaw without the need for other technologies?

It's not just 3D transforms, a simple scale down will exhibit aliasing as well.

There's no flag to control aliasing migitating strategies for CSS in the spec, nor is there any discussion about it as far as I know.

Post reply on HN