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

61–68 of 68 posts

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

#61

Post by derefr »

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…

> draw fonts by rasterizing (in the fragment shader) the bezier curves

So, ideally, browsers would be doing this themselves, after applying the transform to any non-text in the texture, and then compositing with the combined texture?

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

#62

Post by jerf »

jacquesm wrote: post #22
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…

"Less executable code on the client, more powerful markup."

Well, since when it comes to layout, the union of everybody's desires appears to be simply Every Possible Thing, your more powerful markup is going to end up being executable code anyhow. If you specify a Turing-complete set of needs, you're going to need a Turing-complete language to satisfy them.

You can already see this happening even in CSS, and the more they try to pretend that CSS isn't code (even though it increasingly is), the more frustrating it's going to get for everyone when you end up with a bug in your CSS, which you are not allowed to fix due to the fact that we're all pretending it's not code.

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

#63

Post by jcampbell1 »

TimPietrusky wrote: post #9
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…

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

You could make everything oversized, then apply a scale of .25. That will improve the aliasing a bit.

Same for the logo. The scale transform should never exceed 1.0.

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

#65

Post by lucisferre »

skriticos2 wrote: post #52

If I remember correctly, the crawl converged in a point at about 1/3 rd from the top in the original while in this one it scrolls off the top of the screen (at least in the default view). That's a pretty big oversight.

Increase the height of that space at the bottom it looks fine.

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

#66

Post by ggchappell »

chiph wrote: post #60
kaoD wrote: post #35

Earlier quoted context omitted.

http://i.imgur.com/UzZYLW5.png Check the farthest text. It's even worse in motion because the aliasing changes discretely.

Speaking as an old guy who saw Star Wars in the theater, it looked like that in 1977 as well. Not because of aliasing problems, but because they hit the resolution of the 35mm film and transfer process.

Yup. OTOH, the errors didn't change discretely as the text moved.
Post reply on HN