It's missing the Episode IV: A New Hope part...what gives?
No, not the remastered version! Nooooooo!
The subtitle was added to second run theatre prints. Long before the remastering.
Star Wars opening crawl from 1977 in HTML/CSS/JS
31–40 of 68 posts
Re: Star Wars opening crawl from 1977 in HTML/CSS/JS
#32Cool, 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…
"create a standard for a VM that other languages can compile bytecode to. Create an API in this VM for graphics, video, audio."
There already is a standard VM with an API for graphics, video and audio - it's called HTML5, and, as a bonus, it also includes an API for text layout. Sure, if you sat down intending to design such a VM, you might not come up with HTML5, but so what; what concrete improvement would you get by distributing programs as bytecode rather than JavaScript?
Re: Star Wars opening crawl from 1977 in HTML/CSS/JS
#33Ah 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.
[deleted]
Re: Star Wars opening crawl from 1977 in HTML/CSS/JS
#34Earlier quoted context omitted.
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.
We call this a leaky abstraction :)
Re: Star Wars opening crawl from 1977 in HTML/CSS/JS
#35Ah 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.
http://i.imgur.com/UzZYLW5.png
Check the farthest text. It's even worse in motion because the aliasing changes discretely.
Re: Star Wars opening crawl from 1977 in HTML/CSS/JS
#36Cool, 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…
Markup and JavaScript are orthogonal concepts.
Re: Star Wars opening crawl from 1977 in HTML/CSS/JS
#37Cool, 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…
> create a standard for a VM that other languages can compile bytecode to
That sounds a lot like Asm.js [1] Check Emscripten too! [2]
Re: Star Wars opening crawl from 1977 in HTML/CSS/JS
#38Earlier quoted context omitted.
> 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…
Markup and JavaScript are orthogonal concepts.
Lots of concepts that are now part of HTML5 could only be done with Javascript in earlier incarnations.
Re: Star Wars opening crawl from 1977 in HTML/CSS/JS
#39Earlier quoted context omitted.
Markup and JavaScript are orthogonal concepts.
Lots of concepts that are now part of HTML5 could only be done with Javascript in earlier incarnations.
Although you're right, they're still orthogonal concepts. Powerful markup does not replace JavaScript for all use cases.
Re: Star Wars opening crawl from 1977 in HTML/CSS/JS
#40Back in 1994, my 486 had no issue rendering the Star Wars opening crawl in a sweet game, Star Wars: TIE Fighter. Fast forward 20 years, and thanks to the wonders of web, my computer can't even render it correctly. I get a blank screen after the star wars logo. So much for progress.