So we should wait for browser vendors to agree on a new next generation language for the web and wait until everyone updates to a browser that supports it?
Like it or not these developments are turning JS into a bytecode for the web. Maybe one day there will be other language options but why not invest in making the best of what we do have?
So we should wait for browser vendors to agree on a new next generation language for the web and wait until everyone updates to a browser that supports it?
No, we should grab the first thing available and run with it, making sporadic additions and optimizations to do cool-thing-of-he-day, completely ignoring overall architecture and neglecting original purpose behind the technology we use. Next stop: compiler that will translate C code into Excel macros.
Comments
So we should wait for browser vendors to agree on a new next generation language for the web and wait until everyone updates to a browser that supports it?
Like it or not these developments are turning JS into a bytecode for the web. Maybe one day there will be other language options but why not invest in making the best of what we do have?
So we should wait for browser vendors to agree on a new next generation language for the web and wait until everyone updates to a browser that supports it?
No, we should grab the first thing available and run with it, making sporadic additions and optimizations to do cool-thing-of-he-day, completely ignoring overall architecture and neglecting original purpose behind the technology we use. Next stop: compiler that will translate C code into Excel macros.