I'd like to point out a example where using different sources (from older and newer versions of a language) inside one runtime environment is used fairly successfully.
Each OpenGL version comes with a new version of the GLSL language, which may break things. On top of my head this was the case in: - varying -> in/out - gl_FragColor -> gl_FragData[n] - removal of builtins (such as gl_ModelView) The first version of GLSL for a platform does not require marking up with a version (as in OpenGL 2.0, OpenGL ES 2.0). Subsequent versions required the version directive "#version XXX" on top of the source file, if they wanted to use later iterations of GLSL. The advantage of that was that all engines/libraries/snippets you might've used keep working, even as you start using the newer version and gradually fade out support/development/dependencies for older versions. On Tue, Aug 12, 2014 at 2:05 AM, Brendan Eich <bren...@mozilla.org> wrote: > Andrea Giammarchi wrote: > >> I read that and still not convinced this is good for the web or >> developers. >> > > Well, forget me. What did you think of Florian's argument citing Python 3 > vs. 2 uptake problems? I see Perl 6 (full of great ideas that required a > compat break) vs. 5 in the same light. Evolution is hard to beat. > > > /be > _______________________________________________ > es-discuss mailing list > es-discuss@mozilla.org > https://mail.mozilla.org/listinfo/es-discuss >
_______________________________________________ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
