Re: Why are we limited to JS in browsers - would a bytecode ...
by InclinedPlane on Thursday November 11, 2010 @08:25PM
(#1896148)
I'd say Unix and C have more warts, and more serious warts, than Javascript does. But we have come to accept those warts in Unix and C as "the way things are" whereas we generally perceive javascripts warts as such. Arguably the decision to use null-terminated strings in C in order to save one or two bytes of memory per string is an error of much greater than Y2K proportions that we are still paying for.
[ Parent
| on HN ]
Re: Why are we limited to JS in browsers - would a bytecode ...
by silentbicycle on Friday November 12, 2010 @12:20AM
(#1896626)
Agreed, though I think most of Unix's serious warts are actually C's. They're synergistic, though.
Re: Why are we limited to JS in browsers - would a bytecode ...
by silentbicycle on Friday November 12, 2010 @03:17PM
(#1899088)
(Oops: I meant 'symbiotic'.)