If I recall correctly, Microsoft got taken to the woodshed for providing its proprietary Java engine, eventually eliminating it in Windows XP SP1a.
So now we have Chrome's "V8" and Firefox's "TraceMonkey" Java engines entering the fray. Will the Chrome and Firefox fans endure being flogged for their favorite browser's foray into the same territory for which they themselves likely flogged Microsoft just a few years ago?
|
Does Verizon's Voyager stack up to the iPhone? |
|
|
5 IT skills that won't boost your salary 
[1,407]
Women 4 times more likely than men to cough up personal info [589]
Japan's 10 funniest tech-related commercials [Videos] [407]
Throwing away a promo CD is "unauthorized distribution"? [1,265]
Adults too quick to dismiss educational video games [682]
Attack of the iPhone clones [Slideshow] [578]
10 things IT needs to know about AJAX [1,258]
This Year's 25 Geekiest 25th Anniversaries [Slideshow] [409]
|
|
Re: Proprietary Java Engines
@Rick,
V8 and TraceMoneky are JavaScript engines, JavaScript is totally different thing from Java.
Post new comment