The code is quite cool to look at. Love seeing the extensive use of matrices and mathematics to create such a beautiful and mesmerizing display.<p>If anyone is interested in playing around with it, I threw it up at JSFiddle here: <a href="http://jsfiddle.net/zyAzg/" rel="nofollow">http://jsfiddle.net/zyAzg/</a><p>Excellent demo.
> Your browser does not appear to support the required technologies.<p>It would've been nice to have an 'I don't care, proceed anyway' button. The check excludes Safari 7, which runs the demo just as well as Chrome.<p><a href="http://jsfiddle.net/bYHfh" rel="nofollow">http://jsfiddle.net/bYHfh</a><p>^ removes the hasWebGLSupport() invocation.<p>Very nice demo, though!
Thank you for the Youtube fallback! (<a href="https://www.youtube.com/watch?v=IrUehq6vJss&feature=youtu.be" rel="nofollow">https://www.youtube.com/watch?v=IrUehq6vJss&feature=youtu.be</a>)
Honestly very impressive, idea: if made into fullscreen (i.e. without edges visible) and with an added horizon and an emulated sun-rise/sun-set this would make for totally enthralling watching - the "live'ness" of it makes it a thousand times more interesting to the eye than images or pre-recorded video material.
Very nice and fully custom code too! The UI is really clean and fits nicely with the WebGL via CSS transforms I believe. Props to you.<p>BTW geistner waves reference here: <a href="http://http.developer.nvidia.com/GPUGems/gpugems_ch01.html" rel="nofollow">http://http.developer.nvidia.com/GPUGems/gpugems_ch01.html</a>
Reminds me of this shader toy shader. <a href="https://www.shadertoy.com/view/XdsGDB" rel="nofollow">https://www.shadertoy.com/view/XdsGDB</a>
Might be system dependent, though couldn't help but notice a non-trivial difference in the OpenGL rendering quality, between Firefox and Chrome.<p>Chrome 32 beta on OS X, produced an anti-aliased canvas, whereas Firefox 25 had the dreaded jaggies @ 1680x1050
This is a really awesome demo. Great work.<p>I'd love to see it with different ocean floors to be able to see how waves break in different locations based on certain conditions. Someone please make this happen! :D
I knew this is a bit irrelevant, just want to show a pure js ripple effect which I borrowed before: <a href="http://jsfiddle.net/esteewhy/5Ht3b/6/" rel="nofollow">http://jsfiddle.net/esteewhy/5Ht3b/6/</a>
This runs at about 7 frames per second in Chrome on my 10-month-old 13" Macbook Pro at work.<p>Are people with better graphics cards seeing 60 (or even 30) fps? I'd love to be able to see this in all its glory.
Relevant: <a href="http://www.babylonjs.com/Scenes/Worldmonger/index.html" rel="nofollow">http://www.babylonjs.com/Scenes/Worldmonger/index.html</a><p>Scene with water, made with BabylonJS.
Hitting ctrl-+/ctrl-- on chrome leads to interesting results :) Impressive demo, kept staring at it for a while pondering the exciting future the web platform has in it.
I am surprised how this runs smoothly even on lower end PCs.
I was able to view it perfectly smooth on a old Dual Core, integrated graphics and 2GB RAM linux box.
excellent work, thanks for sharing. my wavyness simulation resulted in more literal results [1] so i'm glad to have code to study for improvements.<p>[1]: <a href="https://www.youtube.com/watch?v=EnG6I1nsHy4" rel="nofollow">https://www.youtube.com/watch?v=EnG6I1nsHy4</a>
I remember seeing this run smoothly on a P2 after a very small executable download in late 90's. How far we've come in a big, stupid circle back where we started.<p>Now instead of a small executable, we need a large executable to sit on top of a large API on top of the CPU before even touching the GPU, and a network connection to download all the dependant APIs and libraries every time the page is loaded.<p>The only impressive thing about this demo is how many YCombinator readers are impressed with blinkenlights
computers have now become so powerful that this stuff is easy. you can implement it in a way which, aside from platform, is really quite naive and wasteful - and still get applause.<p>most programmers can come up with a much better solution to this problem if removed from google and forbidden access to gpu gems.<p>this is at least well presented though...<p>its a shame the code has been posted. whilst i normally assume that demos like this are unlikely to be smart or impressive these days - this time i know for sure. its actually a good deal worse than i ever would have imagined.<p>i'm still quite torn whether all this horsepower is a good thing or not.... on the one had we get a demo like this without much in the way of understanding or resourcefulness. on the other hand we have hundreds of man hours being wasted at dev studios because clever efficiency is rapidly becoming a thing of the past...