Slashdot Mirror


Revamped WebKit JavaScript Engine Doubles In Speed

Shin-LaC writes "In a post on their official blog, WebKit developers introduced the 'next generation' of their JavaScript engine, SquirrelFish Extreme, claimed to be twice as fast as its predecessor. The post lists several changes contributing to the performance improvements, including 'bytecode optimization,' a 'polymorphic inline cache' (which sounds similar to V8's 'hidden class transitions'), and a 'context threaded JIT' compiler which generates native code (currently only for x86 processors), and is also applied to regular expressions. The new JavaScript engine is already available in the latest WebKit nightly builds. According to comparative benchmarks, the new engine is around 35% faster than the V8 engine recently introduced in Google Chrome, and 55% faster than Mozilla's TraceMonkey."

270 comments

  1. Bar graphs... by Anonymous Coward · · Score: 5, Funny

    As you can see in this bar graph, our bar is bigger than our competitors' bars.

    1. Re:Bar graphs... by Anonymous Coward · · Score: 2, Funny

      It is not the length that counts but the girth!

    2. Re:Bar graphs... by smittyoneeach · · Score: 1

      Yes, but the axis label mentions execution time.
      Isn't less more?
      Or is more the new less?
      Or Les the Nessman?
      This junction is PN complete.

      --
      Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
    3. Re:Bar graphs... by Anonymous Coward · · Score: 2, Funny

      You wish, first you gotta by me dinner! Sauteed SquirrelFish sounds appropriate.

    4. Re:Bar graphs... by Kooty-Sentinel · · Score: 4, Funny

      I'd prefer to go to a Chinese restaurant and eat some freshly slaughtered TraceMonkey. And for drinks I'd just like some V8.

      --
      Your evaluation period for Productivity 1.0 has ended. Please purchase more coffee to continue using this product.
    5. Re:Bar graphs... by Anonymous Coward · · Score: 0

      Yay Ghost World

    6. Re:Bar graphs... by Hal_Porter · · Score: 1

      Yes, but the axis label mentions execution time.

      Isn't less more?

      Or is more the new less?

      Or Les the Nessman?

      This junction is PN complete.

      I like the way PC gamer sites label each graph LOWER SCORES ARE BETTER or HIGHER SCORES ARE BETTER.

      It reminds me of a priceless ad in a UK computer magazine for DRAM. "All our SIMMs are high quality, not cheap low quality modules with low capacitance and slow refresh cycles!"

      --
      echo -e 'global _start\n _start:\n mov eax, 2\n int 80h\n jmp _start' > a.asm; nasm a.asm -f elf; ld a.o -o a;
    7. Re:Bar graphs... by funfail · · Score: 1

      I like the way PC gamer sites label each graph LOWER SCORES ARE BETTER or HIGHER SCORES ARE BETTER.

      It already says that:

      These graphs are shown in runs per minute for clarity. Longer bars are better.

  2. That's great! by schmidt349 · · Score: 2, Funny

    The next revision of SquirrelFish, said to make Javascript not suck anymore, is due to be released in 2048.

    1. Re:That's great! by caffeinemessiah · · Score: 5, Interesting

      The next revision of SquirrelFish, said to make Javascript not suck anymore, is due to be released in 2048.

      I know you're just trolling, but Javascript is actually getting fun to program in for recreational purposes. It reminds me of assembly programming back in the day, at least that's where its development seems to be in terms of a programming language. It's actually fun to hack, and you can already do some nifty things like pseudo-threading using its window.setTimeout() function and some clever programming. The fact that the engines are getting more powerful just makes it more fun and likely to pay off.

      I remember when C/C++/ASM programming was fun to hack, until the age of monolithic libraries like MFC and OWL (and now things like the JDK and .Net) came and ruined that fun by restricting your freedom. If there's one thing that will make me buy into the whole browser-as-OS thing, it's an efficient, bare-bones and flexible Javascript implementation, kind of like programming in C for your browser.

      --
      An old-timer with old-timey ideas.
    2. Re:That's great! by Anonymous Coward · · Score: 0

      There next version of SquirrelFish won't be 'Extreme' anymore. They'll refuse to listen to their marketing department and call it 'FungusBreath Ultimate Platform'.

    3. Re:That's great! by Niten · · Score: 3, Insightful

      I had a feeling someone would use this as a JavaScript-bashing opportunity. After all, JavaScript is the world's most misunderstood programming language.

    4. Re:That's great! by smittyoneeach · · Score: 1, Funny

      Python3000 will, like, totally kick SquirrelFish2048 in its furry scales.

      --
      Get thee glass eyes, and, like a scurvy politician, seem to see things thou dost not.--King Lear
    5. Re:That's great! by Anonymous Coward · · Score: 1, Insightful

      Nevertheless, Javascript implementations suck pretty hard and that is why all of the various groups are able to show such huge performance improvements.

    6. Re:That's great! by Anonymous Coward · · Score: 3, Insightful

      ... until the age of monolithic libraries like MFC and OWL (and now things like the JDK and .Net) came and ruined that fun by restricting your freedom. If there's one thing that will make me buy into the whole browser-as-OS thing, it's an efficient, bare-bones and flexible Javascript implementation, kind of like programming in C for your browser.

      Bullshit.

    7. Re:That's great! by Anonymous Coward · · Score: 0
    8. Re:That's great! by dmsuperman · · Score: 1

      Doesn't JavaScript have to suck to be looking forward to a revision that's been out for years?

      --
      :(){ :|:& };: Go!
    9. Re:That's great! by phantomfive · · Score: 2, Interesting

      OK, I know you're going to call me a fanboy, but you really need to try Cocoa. MFC is miserable not because it's monolithic, but because it's designed in a way that makes everything miserable. .Net is a little better, but still not fun.

      Cocoa (really NextStep) makes it easy to take control of whatever part you want: it is logically organized and easy to customize any part. Do you want to make a window that covers the whole screen transparently, then lets you draw on it? Simple, and it's programmatically the same as drawing anywhere else. Do you want to flip your window and do all kinds of weird effects? It is amazing how easy it is. Cocoa gives you the feeling of complete control again. And it is fun.

      --
      Qxe4
    10. Re:That's great! by try_anything · · Score: 4, Insightful

      I remember when C/C++/ASM programming was fun to hack, until the age of monolithic libraries like MFC and OWL (and now things like the JDK and .Net) came and ruined that fun by restricting your freedom.

      How do libraries and application frameworks restrict your freedom? Your boss makes you use them? Sorry, I don't follow your argument at all. If you want to write your own socket library, regular expressions library, and logging framework, go ahead and do it. Nobody's stopping you.

      If modern amenities have made you bored with programming, I suggest attacking a problem domain that hasn't yet been made trivially easy. Get a four-core box and convert a single-threaded application into one that uses all four cores efficiently. That's something that Java and .NET won't solve for you. Whenever one problem is rendered trivial by Moore's law or by some helpful library author, there is always a bigger problem to tackle.

    11. Re:That's great! by operator_error · · Score: 2, Insightful

      OK, I know you're going to call me an old curmudgeon, but where can I run your Cocoa code? Pretty much all the customers in my market use Windows, but might be open to Linux. And we're all focused more heavily on servers too. New Apple hardware is going to be a tough sell too.

      At least with javascript, I can expect a universal, albeit lowest-common-denominator client-base.

    12. Re:That's great! by Waccoon · · Score: 3, Interesting

      It's actually fun to hack, and you can already do some nifty things like pseudo-threading using its window.setTimeout() function and some clever programming.

      I had to do this, because JavaScript is single-threaded.

      A Java applet I need to support kept trying to make a JavaScript call to the browser, and kept failing, which crashes a background timer I had implemented in JavaScript. I had to "restart" JavaScript using a mouseover event and use threading to keep it from using up all the CPU time. It was such a stupid hack, but it worked.

      I eventually figured out the function name the applet kept calling and was able to shut it up. It still boggles me that any JavaScript from anywhere, such as from an ad, can crash the language and leave you with no JavaScript support at all. It's very hard to count on a language when browsers implement is so badly, especially when you have no choice but to support really old software that keeps doing bad things that upset newer, stricter versions of a scripting language.

      Now, does this WebKit update fix the JavaScript threading issue? Then I'll be impressed.

    13. Re:That's great! by Anonymous Coward · · Score: 0

      If modern amenities have made you bored with programming, I suggest attacking a problem domain that hasn't yet been made trivially easy. Get a four-core box and convert a single-threaded application into one that uses all four cores efficiently. That's something that Java and .NET won't solve for you.

      Perhaps that's why I have a Ph.D. in CS.

    14. Re:That's great! by brainnolo · · Score: 3, Informative

      You should take a look at http://cappuccino.org./ Is really interesting and brings the best of both worlds.

    15. Re:That's great! by multipartmixed · · Score: 4, Informative

      JavaScript isn't single-threaded.

      Only one JavaScript thread is used by firefox (and maybe other browsers -- I don't know).

      In fact, spidermonkey is thread-safe and you can run multiple JavaScript threads outside the confines of the browser. In fact, I have written a class for spidermonkey which lets you create real OS threads running JavaScript functions.

      > It still boggles me that any JavaScript from anywhere, such as from an ad, can crash the language
      > and leave you with no JavaScript support at all

      Out of curiosity, how many programming languages do you know that will let you keep executing code once a syntax error has been reached, or an exception has been thrown but not caught?

      The problem here isn't language design, it's poor programming. And try..catch block will work wonders around other-peoples-crappy-code.

      > It's very hard to count on a language when browsers implement is so badly, especially when
      > you have no choice but to support really old software that keeps doing bad things that upset
      > newer, stricter versions of a scripting language.

      Aside from function.arguments and === in JavaScript 1.2, I'm having a hard time thinking of a JavaScript language change which was broke backwards compatibility. That includes IE. Although it would be nice if IE would fix their stupid [1,2,3,].length bug.

      --

      Do daemons dream of electric sleep()?
    16. Re:That's great! by jsebrech · · Score: 1

      I had to do this, because JavaScript is single-threaded.

      With google gears workers you can run multiple javascript threads easily (synchronized with message passing). Google gears is integrated by default in chrome, and just a plugin install away on other browsers.

      Your specific problem sounds related to bad 3rd party code, not due to a lack of threading.

    17. Re:That's great! by Waccoon · · Score: 1

      Sorry, I stand corrected in that this is an implementation issue, and not a JavaScript issue. Firefox really drives me nuts at times because even with strict warnings turned off, it will complain a lot. IE and Safari have their own problems not entirely related to the usual compatibility issues.

      And try..catch block will work wonders around other-peoples-crappy-code.

      That doesn't work when an applet or other embedded object uses JavaScript. In Firefox, if one object causes a JS exception, everyhing stops working, which is very annoying. I'd be nice if I could get a new Java applet to work with, but that's not an option.

      That's why I don't like the idea of having all JavaScript includes behaving as if it's one giant script. This is the hyperlinked web, and not all the information that shows up on a site is specific to your domain. Every major site that uses advertising feels this pain at some point, because advertisers do not allow you to host their ad service on your server, and web browser developers didn't take that into account when they integrated scripting into the browser.

      I'm not sure that this new trend of moving to separate processes will fix anything in these cases, because you can't really differentiate between your code and someone else's.

      Aside from function.arguments and === in JavaScript 1.2, I'm having a hard time thinking of a JavaScript language change which was broke backwards compatibility. That includes IE.

      Again, browsers have changed a lot over the years, and some methods that worked in the past no longer function these days. Scripts that were perfectly legal a couple years ago will throw some kind of security exception, and that causes the whole site to grind to a halt. That's preferable behavior if you're making a web app, but a major headache when you just have some objects trying pass messages.

    18. Re:That's great! by Anonymous Coward · · Score: 2, Interesting

      That's great, you spent lots of time in school. Now how much real-world, business driven application development experience do you actually have?

      When I finally went back and finished by BS in CS (just so I could get promoted--glass ceilings and all), one of my last classes was in search engines. 22 people in the class, 3 undergrads (me and two others) the recent masters program students.

      The other 2 undergrads dropped out leaving me the only undergrad. When we had to deliver a search engine (built over a corpus of medical documents) I was the only student to have a finished working one. I had to explain to a number of the masters students how to open a stream in C++ and read in the words one at a time.

      Not one other student delivered a fully working piece of code, a point the professor (head of graduate studies) commented on.

      Now granted, I have over 25 years experience in software development, but you'd think that students in masters or Ph.D. programs could at least write code that can read data from a file.

      So, just because you have a Ph.D. in CS doesn't buy you any brownie points. I've noticed a large number of postings to various forums I monitor from folks saying things like "I'm a Ph.D. candidate and working on a thesis around the topic you are explaining. Mind if I ask you some questions?"

      Ph.D.'s today don't mean what they used to mean. Use that Ph.D. to deliver some real innovations to the CS world then I'll be impressed.

      Just an aside, even though the Grad Studies head asked me to consider returning to work on a graduate degree (and the head of the CS department asked me to come back and teach Java courses) I decided to pursue an MBA instead. I already know the CS work, and the MBA work is allowing me to understand the business side of my job better.

    19. Re:That's great! by STFS · · Score: 4, Insightful

      Please mod parent up, it's true, this is bullshit! Monolithic libraries in C++ restrict your freedom? How in the world do you get to that conclusion? FYI, almost nobody uses MFC, and if it bogs you down, well duhhh... don't use it! C++ is almost exactly the way it used to be, the language hasn't changed at all. You can still do everything by hand like you used to if that's what you want. The "monolithic" libraries you speak of tend to help the rest of us get things done and I for one, welcome a more diverse selection of these.

      --
      You don't think enough... therefore you better not be!
    20. Re:That's great! by multipartmixed · · Score: 1

      > implementation issue, and not a JavaScript issue.

      This is a common error, which I find myself correcting regularly. It's clearer to me than the average joe, because I write non-browser JavaScript on a regular basis.

      > That's why I don't like the idea of having all JavaScript includes behaving as if it's one giant script.

      The problem there is that the browser inventors came up with the web-page = program-scope equivalence, with only one program isolation container: iframe. Basically, document is to process as web-page is to operating system.

      Furthermore, JavaScript was meant to be used in the browser to only to manipulate the document.. And it doesn't have to be JavaScript. It could just as easily be VBScript...or even lua or python if somebody wrote the bindings and banged it into a browser.

      > I'm not sure that this new trend of moving to separate processes will fix anything in these cases, because you can't
      > really differentiate between your code and someone else's.

      Right. This problem isn't going to be solved without inventing a new container. Or at least making use of the crappy one we have now (iframe).

      > Again, browsers have changed a lot over the years, and some methods that worked
      > in the past no longer function these days

      JavaScript methods, or DOM methods called from JavaScript? There is a huge difference!

      JavaScript methods are things like Array.push or String.length. DOM methods are things like document.getElementById. Don't blame the DOM on JavaScript. Just like you shouldn't blame MFC on C++.

      > Scripts that were perfectly legal a couple years ago will throw some kind of security exception,
      > and that causes the whole site to grind to a halt.

      That's because the browsers no longer allow those things. Has nothing to do with the language. I'm sure you'll get the same exceptions calling those same methods from VBScript.

      Think of it this way, if root changes a file in your home directory so that you can no longer edit it... is that a problem with bash, or root? Me, I'd grab a pipe, find root, and bash him with it.

      I don't mean to come off as a pedant, I'm trying to help people see the world as it really is... so that JavaScript can be taken more seriously, AND so that the people in charge of the browser DOM (etc) design will come up with better application containers and method passing techniques.

      (Ever tried to write an AJAX app that spanned domains? It's ridiculously difficult and requires extensive hoop jumping)

      --

      Do daemons dream of electric sleep()?
    21. Re:That's great! by TheRaven64 · · Score: 2, Informative

      Cocoa is an implementation of the OpenStep APIs. GNUstep is another implementation and runs on Windows. In Ãtoilé svn we have a theme engine for GNUstep (Camaelon), although there is not yet a native Windows theme. If you're targeting GNUstep, you aren't limited to Objective-C either - I have written a native compiler for Smalltalk which produces equivalent code to Objective-C for operations which are not heavy on arithmetic (currently much slower for arithmetic, but if you're doing a lot of number crunching you can write some methods in ObjC - with inline asm if you really need the speed - and others in Smalltalk in the same class), and we plan on adding JavaScript and Io support in the relatively near future.

      Back on topic, polymorphic inline caching is absolutely nothing to do with hidden class transformations. PIC is a technique originally from the Self team (as is HCT - not surprising, since JavaScript is basically an ugly version of Self with some weird corner cases). In a dynamic language, every message send (that's method call toy any Java programmers that wandered in) is two operations; a lookup mapping the selector (method name) to a function, and a call to the function. The Self guys discovered that at most call sites only a small number of different functions were called. In Smalltalk, you would cache a small set of (class, function) pairs, and then you have a quick way of looking up the correct mapping that would work in most cases. In Self (or JavaScript) it's slightly more complicated, because the cache only works for objects which share the same prototype and do not declare a replacement mapping (HTC can make this simpler). In the Ãtoilé dynamic languages runtime I proposed and implemented a simple (and concurrency-safe) means of invalidating these caches in a statically-compiled language. This will be used in Objective-C code compiled with clang and Smalltalk code compiled with the Pragmatic Smalltalk Compiler when I finish adding support for this runtime to both (before Christmas hopefully).

      --
      I am TheRaven on Soylent News
    22. Re:That's great! by Anonymous Coward · · Score: 0

      If there's one thing that will make me buy into the whole browser-as-OS thing, it's an efficient, bare-bones and flexible Javascript implementation, kind of like programming in C for your browser.

      Then consider Lua. Lua would have made a better Javascript than Javascript. While the syntax is different, the semantics between Lua and Javascript are almost the same (basically the languages are twins). Lua is a whole lot more pure though. Simple and with LuaJIT way faster than any Javascript engine I have tested. Lua is incredibly small and easy to embed too. It has the same power as Javascript though.

      I believe the Javascript language itself has critical design flaws that will keep it from reaching the performance levels of better designed scripting languages. Read the history of Javascript. It grew out of Netscape as a hack. Very poor planning left lots of room for all kinds of crap patches and hacks leading up to the huge EMCA specification. It's a big mess really.

    23. Re:That's great! by BZ · · Score: 1

      > JavaScript methods, or DOM methods called from JavaScript?

      For what it's worth, the former as often as the latter. Things like indirect eval, for example, used to be allowed in SpiderMonkey and now aren't.

    24. Re:That's great! by Anonymous Coward · · Score: 0

      Wow those sour grapes are really hanging low, bub.

    25. Re:That's great! by phantomfive · · Score: 1

      No, I definitely agree with you. Cocoa code is fun to play in, but when it comes right down to it, you have to code with what you have.

      However, Cocoa IS fun to play with, and in the future more and more of the programming world is going to look like that. Java and .net have already borrowed from it somewhat (although in those days it was called OpenStep or NextStep), and it's based on principles that have been around since at least small talk in the seventies, but still aren't really common in mainstream development.

      --
      Qxe4
    26. Re:That's great! by phantomfive · · Score: 1

      Thanks for the link, that looks awesome.

      --
      Qxe4
    27. Re:That's great! by Anonymous Coward · · Score: 0

      Cocoa is an implementation of the OpenStep APIs. GNUstep is another implementation and runs on Windows. In Ãtoilé svn we have a theme engine for GNUstep (Camaelon), although there is not yet a native Windows theme. If you're targeting GNUstep, you aren't limited to Objective-C either

      Cocoa isn't limited to Objective-C.

    28. Re:That's great! by sjames · · Score: 1

      I remember when C/C++/ASM programming was fun to hack, until the age of monolithic libraries like MFC and OWL (and now things like the JDK and .Net) came and ruined that fun by restricting your freedom.

      So toss MFC and OWL, .net etc overboard. Consider writing Linux apps.

    29. Re:That's great! by mad.frog · · Score: 1

      wow... Objective-C *and* Smalltalk?

      What more could I ask for?

    30. Re:That's great! by mad.frog · · Score: 1

      It has the same power as Javascript though

      This is a content-free statement. Technically, every Turing-complete language does. More detail, please.

    31. Re:That's great! by Anonymous Coward · · Score: 0

      I was using Javascript 6 years ago to make Flash/Actionscript type websites without a plug-in.

      I haven't touched code in over 5 years, or worked in the industry since then (I deliver pizza now) but it seems NOTHING has really changed much. People are NOW embracing a technology that is ancient. No wonder I quit.

      I never hear anybody talk about XML anymore, because CSS has always been simpler and faster, I wonder if the DOM is still the same...probably is, just has some add-ons.

      I can only hope the simplicity of PERL will get this kind of revival (i got a chubby with the regex speed improvement).

    32. Re:That's great! by Ant+P. · · Score: 1

      A pony!

    33. Re:That's great! by LWATCDR · · Score: 1

      "I remember when C/C++/ASM programming was fun to hack, until the age of monolithic libraries like MFC and OWL (and now things like the JDK and .Net) came and ruined that fun by restricting your freedom. "
      Huh????
      You know that you don't have to use them. They are an option. Options means more freedoms not less. Oh MFC sucks really bad. It has a fair amount of bugs and is being replaced by .NET . I have no opinion on the new frame work since I don't use it.
      Hey you can still use Win32 if you want under windows. I know people that swear by it. As well as at it.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    34. Re:That's great! by LWATCDR · · Score: 1

      But don't you have to use Objective C for Cocoa? And you must be on a Mac.
      I have heard nothing but good things about Cocoa and OpenStep but being limited to Objective C is a problem for me.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    35. Re:That's great! by LWATCDR · · Score: 1

      GnuStep may be an option for you.
        It works on Linux.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    36. Re:That's great! by phantomfive · · Score: 1

      Sorry, I am not sure why objective C is such a problem for you. It's a good language; maybe if you tell me your concern, I can clear it up for you.

      If you have to use windows, then Cocoa is clearly not to you (I fall into that category at work), but without doubt Cocoa is significantly more fun to work with than anything on Windows.

      --
      Qxe4
  3. Tracemonkey is slower than V8? by martinw89 · · Score: 4, Informative

    Excuse me, but I think that Tracemonkey is actually faster than V8. Has Tracemonkey really fallen that far behind in two weeks?

    1. Re:Tracemonkey is slower than V8? by Anonymous Coward · · Score: 3, Insightful

      He who controls the test suite, controls the outcome.

    2. Re:Tracemonkey is slower than V8? by JackassJedi · · Score: 1

      Does the result really say that Tracemonkey is slower than V8? Not sure, but just a thought.

      --
      Power corrupts the few, while weakness corrupts the many.
    3. Re:Tracemonkey is slower than V8? by Spy+der+Mann · · Score: 4, Informative

      Excuse me, but I think that Tracemonkey is actually faster than V8. Has Tracemonkey really fallen that far behind in two weeks?

      Yes. On XP (that's the best case), Tracemonkey takes 1.340 seconds to do a Sunspider run, which equals to 32.6 Sunspider rus per minute. And Squirrelfish Extreme does 63.6 Sunspider runs per minute. That makes Squirrelfish Extreme 1.95 times faster than Tracemonkey.

      Time for Mozilla to catch up again. In any case, the winner is... the public! (the engines won't get any slower)

    4. Re:Tracemonkey is slower than V8? by flooey · · Score: 5, Funny

      (the engines won't get any slower)

      Clearly you haven't seen the plans for IE9.

    5. Re:Tracemonkey is slower than V8? by BZ · · Score: 2, Interesting

      Are you running the standard Firefox nightlies? Or the actual branch active tracemonkey development is happening on?

      See my other post on this article about measurement bias if one measures right after landing big changes. ;)

    6. Re:Tracemonkey is slower than V8? by jhol13 · · Score: 1

      How would e.g. Rhino http://developer.mozilla.org/en/Rhino_JavaScript_Compiler compare to this (performance wise)?

    7. Re:Tracemonkey is slower than V8? by Anonymous Coward · · Score: 0

      Not directly, but it says that SquirrelFish is 30% faster then V8, and 50% faster then Tracemonkey, implying that V8 is faster then Tracemonkey

    8. Re:Tracemonkey is slower than V8? by Midnight+Thunder · · Score: 1

      Clearly you haven't seen the plans for IE9.

      IE constantly reminds me of our politicians: over promising and under delivering.

      Truth is with Gecko and WebKit based browser getting such an important share of the market, Microsoft knows they have work to do. Microsoft hadn't made any noticeable effort on IE until Firefox and Safari started changing the web usage stats. IE is still generally has the largest market share (depending on which site's stats are used), but any serious web developer knows that Firefox counts for a lot.

      I work for a company, developing a large scale web site, that would have previously only cared about IE, but with the rise of Firefox we also have to test for this browser. This is a good thing, since even if the QA team only tests for IE and Firefox, things that work in Firefox generally work in other standards compliant browsers. I unofficially I test in Safari and Opera, but that doesn't represent the general company.

      --
      Jumpstart the tartan drive.
    9. Re:Tracemonkey is slower than V8? by Anonymous Coward · · Score: 0

      Hm, didn't know Sunspider uses those special 43.6-second minutes. Must be the funnest time ever.

    10. Re:Tracemonkey is slower than V8? by anaesthetica · · Score: 1

      Joseph Stalin, now an Anonymous Coward on Slashdot.

    11. Re:Tracemonkey is slower than V8? by shutdown+-p+now · · Score: 2, Funny

      What, they're going to dynamically convert HTML/CSS/JS to Silverlight/WPF/C# on the fly, and render that?

  4. Faster = more memory? by Starmengau · · Score: 2, Insightful

    One of the things we've seen in the past few releases of any browser is that new features seem to increase the already monumental footprint of current web browsers. As far as I've seen, JIT compilers use a whole freaking lot of memory. While I suppose this is acceptable for the whole "Web 2.0 means the web is the only useful thing on your PC!" crowd, I'd like to have a few (3 or 4)browser tabs open while I'm playing a game, for example, without the browser killing my gaming experience.

    1. Re:Faster = more memory? by martinw89 · · Score: 5, Insightful

      No, I will not get off your lawn. Space/speed is a tradeoff. At the moment, we have even bottom of the barrel desktops selling with large amounts of memory. With the eventual rise of 64 bit, expect the amounts to go up even more. There's no reason to avoid taking advantage of this. What's the point of having this huge (seriously, look at the memory difference from now and 10 years ago) amount of memory to just let it sit there, save the occasional multimedia editing task?

      As for your game, it seems to be using quite a huge chunk of memory as well. You know, one of the things we've seen in the past few releases of any modern 3D game is that new features seem to increase the already monumental footprint of current games. And hell, I'm using my browser at least 10 times longer a day than I'm playing a game. I want my browser to be snappy, I don't mind not visiting Super Ultra JS Web App 3.6 if I'm going to be playing a resource intensive game. In fact, I probably wouldn't be using my browser at all anyway.

      But that last paragraph is just my personal experience, YMMV

    2. Re:Faster = more memory? by Jeffrey+Baker · · Score: 5, Informative

      Firefox 3.1 (pre-release) uses less memory than Firefox 3, which uses less memory than Firefox 2. Compiled javascript takes a tiny fraction of the total memory used by a web browser. The vast majority is uncompressed bitmaps and string fragments.

    3. Re:Faster = more memory? by Anonymous Coward · · Score: 5, Insightful

      Anyone using the term "gaming Experience" deserves to have it ruined.

    4. Re:Faster = more memory? by DiegoBravo · · Score: 4, Funny

      And they have plans to run Firefox 5.x in a Commodore 64.

    5. Re:Faster = more memory? by MightyYar · · Score: 2, Funny

      One of the things we've seen in the past few releases of any browser is that new features seem to increase the already monumental footprint of current web browsers.

      It's somewhat mitigated by the appropriation of other tasks. For instance, in 1994 I'd run a copy of Eudora, a copy of Netscape, and a copy of a word processor on my Centris 650 with 8MB or RAM. But now, I can do all of these things in my web browser - so it's okay if it takes a little bit more RAM. And to think that people decried Netscape Suite for taking on too much!

      Here, let me fire up my Activity Monitor app and see what Firefox is... SWEET JESUS! 366 MB!!! OH MY FUCKING GOD, WHAT HAVE WE BECOME???

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
    6. Re:Faster = more memory? by phoenixwade · · Score: 3, Funny

      And they have plans to run Firefox 5.x in a Commodore 64.

      Must be scope creep - the original spec was for the timex - sinclair z1000

      --
      A positive attitude may not solve all your problems, but it will annoy enough people to make it worth the effort.
    7. Re:Faster = more memory? by hairyfeet · · Score: 3, Interesting

      I know this is going to be labeled troll,but frankly I don't care. Why is everybody tripping over themselves trying to make faster and faster JavaScript,when the security sucks? I have been able to cut down my customers infections by a good 80% just by installing Noscript and teaching them how to use it. Every day we see more and more JavaScript exploits out in the wild,and yet the only thing anyone seems to be concerned with is speed? JavaScript is getting as bad as ActiveX was in its heyday,and Noscript and sandboxing is really only adding a bandaid to the bleeding wound.

      We need to look at how JavaScript is used on the web and find new ways to lock it down and make it more secure. If we don't,mark my words,it will be talked about in 5 years just like ActiveX. Sounded like a good idea at the time,and then the malware ruined it for everybody. But as always this is my 02c,YMMV

      --
      ACs don't waste your time replying, your posts are never seen by me.
    8. Re:Faster = more memory? by Klaus_1250 · · Score: 1, Troll

      Run one of the Javascript benchmarks in a browser and you'll be surprised how much memory your browser can eat up. I've seen Firefox @ 450MB and Chrome @ 600MB, just by running some heavy Javascript code. While the speed increases are great, 500MB memory usage for just a browser is a lot.

      --
      It only takes one man to change the Wisdom of the Crowd to Tyranny of the Masses.
    9. Re:Faster = more memory? by Tangent128 · · Score: 1

      Except that a lot of speed gains are accomplished by starting over with a modern engine design, meaning the engine code is all written in the security-aware era.

    10. Re:Faster = more memory? by andy_t_roo · · Score: 1

      and as a scripting language, not an arbitrary binary one you can (potentially) completly sandbox the apps as part of the design and implementation of the language.

    11. Re:Faster = more memory? by SoupIsGoodFood_42 · · Score: 1

      Well, I run OS X and sometimes it's a pain having to wait for Dashboard to load. Since it runs on WebKit, it should make that faster. There are probably many other examples of non-browser based things that I'm sure I could find.

    12. Re:Faster = more memory? by Anonymous Coward · · Score: 0

      Space/speed is a tradeoff.

      Not always. Is it in this case? I'd be glad to read an explanation, but the handwaving that you are engaging in is less than convincing.

    13. Re:Faster = more memory? by Anonymous Coward · · Score: 0

      If anyone takes this joke another step, I swear I will find you and beat you down.

    14. Re:Faster = more memory? by Koiu+Lpoi · · Score: 1

      Run one of the Javascript benchmarks in a browser and you'll be surprised how much memory your browser can eat up.

      Why would I be surprised? Where else is it going to store that data? Why else do I have 3 gigs of ram in my computer?

    15. Re:Faster = more memory? by francium+de+neobie · · Score: 1

      You'll have to runs 10 miles in the snow, 10 feet deep, uphill, both ways, to find me and beat me down.

    16. Re:Faster = more memory? by blahbooboo · · Score: 1

      How do you do this? I have 3 tabs open and Firefox 3 uses 91mb.

      Your point about extra memory usage is a good one, just curious how people manage to get Firefox to "use so much much memory."

    17. Re:Faster = more memory? by jsebrech · · Score: 4, Insightful

      Every day we see more and more JavaScript exploits out in the wild,and yet the only thing anyone seems to be concerned with is speed?

      Those aren't javascript exploits, they're security issues in other parts of the code that are easiest to trigger via javascript, and that you will resolve with proper sandboxing, which all browser makers are working on. Exploits in pure javascript are pretty rare.

      I think we're talking about a trade-off between usefulness and security anyway. Disabling javascript to gain security is a bit like putting foam on the end of a hammer to avoid hurting your thumb. It sort of misses the point.

    18. Re:Faster = more memory? by MightyYar · · Score: 1

      Honestly, I don't know. I was looking at total memory (including virtual) and I suspect that you were only looking at active memory.

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
    19. Re:Faster = more memory? by sammyo · · Score: 1

      >Space/speed is a tradeoff.

      Assuming an optimum algorithm.

      There are very likely many optimizations possible before the only way to increase speed is using large memory techniques. Although it's unlikely the code and memory footprint will shrink.

    20. Re:Faster = more memory? by init100 · · Score: 1

      What's the point of having this huge (...) amount of memory to just let it sit there

      Modern operating systems never let the memory stay unused. Any memory not used by applications or the system is used as a block cache for hard drives and optical disks, thus speeding up their operations immensely. Thus, even if you are just using applications with small memory footprints, having a large amount of memory installed does not mean that this memory is unused.

    21. Re:Faster = more memory? by RiotingPacifist · · Score: 1

      While I suppose this is acceptable for the whole "Web 2.0 means the web is the only useful thing on your PC!" crowd, I'd like to have a few (3 or 4)browser tabs open while I'm playing a game, for example, without the browser killing my gaming experience.

      Try upgrading to a modern OS, when you launch the 3D game if the browser is not in use its memory should put into swap, and if you have an OS with a decent IO handler (not linux, or at least Ubuntu in my experience) the swapping of the memory will barely be noticeable. If your going to compare about memory usage then you should really be talking about multitasking, so a genuine complaint would be OO and FF both using too much memory, but this is slashdot so we all use emacs vim anyway

      --
      IranAir Flight 655 never forget!
    22. Re:Faster = more memory? by Cthefuture · · Score: 1

      No, I will not get off your lawn. Space/speed is a tradeoff. At the moment, we have even bottom of the barrel desktops selling with large amounts of memory. With the eventual rise of 64 bit, expect the amounts to go up even more. There's no reason to avoid taking advantage of this. What's the point of having this huge (seriously, look at the memory difference from now and 10 years ago) amount of memory to just let it sit there, save the occasional multimedia editing task?

      You're missing a huge part of what is happening with technology these days. The most popular computing platforms are becoming hand-held devices (cell phones, etc). These need all the help they can get as far as performance goes (memory and CPU are limited; fast and getting faster but still limited).

      Designing anything for a standard old-school desktop computer these days would be a huge mistake.

      --
      The ratio of people to cake is too big
    23. Re:Faster = more memory? by martinw89 · · Score: 1

      Except that JS is not NEARLY as tied into the system as ActiveX was. Period. It never will be either, just by the cross platform nature of it.

      And why is it that the anti JS people have to find a way to pop into every JS discussion, even if it's not about security?

    24. Re:Faster = more memory? by hairyfeet · · Score: 1

      I'm not anti JS,I'm just an old guy who remembers when we went down the same road with ActiveX. And as for the above poster,I know it isn't JScript that is being exploited,but the underlying code,but it wasn't ActiveX that was the fault either. Like JScript it was the gateway. Which is why I'm teaching my customers to use Noscript because JScript is simply too dangerous at this time. And sandboxing simply is a bandaid and will be broken,as from the looks of this blog they have a possible way to break out of the Google sandbox. It took them...what? A week?

      I think the problem is a lot deeper than a bandaid like sandboxes will fix. We need to look at the way JScript is used on the web and find ways to lock it down. Maybe a setting that will only allow scripts to run on the domain you are on to help with drive by downloaders? Or perhaps a "penalty box" where the javascript is kept in a no execute bit of memory while it is scanned by an online/offline malware scanner,with the ability to choose which scanning engine you want to keep malware from being written for the engine? I am sure there are a lot of guys out there a lot smarter than me that can come up with new and innovating ways to make JScript more secure. We simply have to get them interested in it instead of this "Damn the CPU and memory! JScript in our browser must be faster than (insert competitor) at all costs!" BS.

      Because if you ask the average user(not us slashdot guys,but folks that just use their machine and want it to go) if they would rather have a faster browser,or one that would keep them from constantly getting malware,I'm pretty sure they would pick the latter. I know it is true in my case,as I'm getting plenty of referrals from those I gave Noscript to that are happy not to be infected. But as always this is my 02c,YMMV

      --
      ACs don't waste your time replying, your posts are never seen by me.
    25. Re:Faster = more memory? by blahbooboo · · Score: 1

      Just using task manager in Windows Xp. Shows Firefox.exe with 4 tabs uses 120mb of ram.

      Maybe its just an OS X thing...

    26. Re:Faster = more memory? by newr00tic · · Score: 0

      'Firefox > 6000' runs on an Abacus.

      --
      A horse can't be sick, you know, even if he wants to.
    27. Re:Faster = more memory? by MightyYar · · Score: 1

      Yeah, OS X is notorius for over-reporting memory usage. I don't really know what I'm talking about, but my understanding is that it basically reports every bit of memory that was ever touched by the application, even if the application has released that memory... Vista gives you an accurate snapshot of what the application is currently using, and XP falls somewhere in between - giving you a report of what the application currently is reserving.

      But I was just going for the funny bone :)

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
    28. Re:Faster = more memory? by Overly+Critical+Guy · · Score: 1

      So much of that is just caching. I don't know why people freak out so much over browser memory. Unused memory is wasted memory.

      --
      "Sufferin' succotash."
  5. Competition by Per+Wigren · · Score: 3, Insightful

    This is a wonderful example of what happens when there are open standards and healthy competition! The consumer is the winner!

    --
    My other account has a 3-digit UID.
    1. Re:Competition by TubeSteak · · Score: 5, Funny

      This is a wonderful example of what happens when there are open standards and healthy competition! The consumer is the winner!

      Is that why /. "consumers" mostly use NoScript?
      Malware: Now 35% faster.

      --
      [Fuck Beta]
      o0t!
    2. Re:Competition by Billhead · · Score: 5, Insightful

      Just because NoScript users are loud doesn't make them a majority.

    3. Re:Competition by Bill,+Shooter+of+Bul · · Score: 4, Insightful

      I use NoScript as a javascript firewall. No stupid javascript from sketchy sites lined to in slashdot stories or random blogs. I don't trust their javascript any more than I trust the editors to edit. Wait, actually I trust it less than slashdot editors to edit.

      --
      Well.. maybe. Or Maybe not. But Definitely not sort of.
    4. Re:Competition by willyhill · · Score: 2, Insightful

      I hear even Microsoft is getting into the game with IE8, supposedly the script engine on that one is much faster than the IE6/7 one, almost on par with FF2.x.

      Long gone are the days of stagnation. Competition is good, let's embrace it and be happy about it instead of complaining (as some people seem to be doing here) about the memory footprint and whatnot.

      Maybe soon the browser will become a viable platform for application delivery, which Netscape promised us back in the early 90s.

      --
      The twitter monologues. Click on my homepage and be amazed.
    5. Re:Competition by lilomar · · Score: 4, Insightful

      Exactly NoScript doesn't really mean No-Scripts, it means No-Scripts-I-Don't-Explicitly-Allow. Just because I don't want anyone with a website to be able to run whatever they want on my box, doesn't mean that I don't ever use JS.

      --
      The creator of this post (Jacob Smith) hereby releases it, and all of his other posts, into the public domain.
    6. Re:Competition by Anonymous Coward · · Score: 0

      I find using NoScript way more annoying than the most annoying javascript I've ever encountered. Many of the web sites I navigate to don't work until I enable like 50 scripts that make simple stuff work. Hell, my Google home page is included in that. It is 50x worse than UAC ever was.

      If by "consumers" you mean "power users" aka slashdot posters then yes you are correct.

    7. Re:Competition by MrZaius · · Score: 1

      How about competition in Linux? All I ever see is the antiquated KHTML that got forked off into Webkit and Gecko, Gecko, Gecko.

      Why on earth do projects like Epiphany even exist, if they're just going to use the exact same rendering engine as every other mainstream browser in Linux?

      Where can you find a decent, reasonably mature Webkit implementation in Linux?

    8. Re:Competition by Anonymous Coward · · Score: 0

      You're right. Some of us Firefox users simply uncheck the box next to JavaScript in the options window.

    9. Re:Competition by johannesg · · Score: 1

      I'm sure happy it is faster, but can anyone point me to a site where it actually matters? I tried Chrome and I couldn't find any site that behaved noticably faster than in Firefox. Maybe my 3 year old PC (and even then "good not state of the art") PC is simply too fast for the web? Or maybe I visit the wrong sites?

    10. Re:Competition by Randle_Revar · · Score: 1

      >Why on earth do projects like Epiphany even exist,
      because they want a browser that had better gnome integration, and was lighter weight because it used GTK, and not XUL.

      Anyway, just hold your horses, Epiphany will be webkit based soon enough. And there has been a fair amount of unforking between khtml and webkit.

    11. Re:Competition by Anonymous Coward · · Score: 0

      "Malware: Now 35% faster." - by TubeSteak (669689) on Friday September 19, @08:25PM (#25080643)

      He was modded up as "FUNNY", but, I still think TubeSteak's right on this statement (personally):

      Instead of working on the speed in javascript, fix its security shortcomings & that of the Document Object Model, first... work on speed, afterwards.

      (Anyone can hit the security vulnerability reporting sites, like SECUNIA.COM for instance, & see that a GOOD 90% of what constitutes malware attacks comes directly from JavaScript related attacks on bogus websites &/or bum adbanners that have these attacks in them (in combination w/ IFrames etc. et al)).

      APK

    12. Re:Competition by Per+Wigren · · Score: 1

      No, you just lack visions. :) The enormous speed boost the major JavaScript engines has gotten just the last few months, with plenty of optimizations still on the TODO-lists, will allow developers to create far more advanced web applications in the future than is feasible right now, without having to resort to proprietary crap like Silverlight.

      Although some junior developers surely will abuse this and make overly complex web sites that risk triggering epilepsy and make it hard to find and read the information they were supposed to present in the first place, it will also be a great benefit to applications like Google's online office apps, webmail and similar. Also JavaScript heavy sites like Facebook will be much nicer to use as they won't eat as much CPU anymore.

      This will also be great for desktop applications written mostly in JavaScript, such as Firefox, Songbird and Komodo IDE.

      --
      My other account has a 3-digit UID.
    13. Re:Competition by Anonymous Coward · · Score: 0

      Just because noscript critics are plentiful doesn't make them smart.

  6. Re:Solid Benchmarks by Anonymous Coward · · Score: 0

    offtopic, no mention of javascript at link dest.
    pls mod parent down if you see fit.

  7. Mmm... by actionbastard · · Score: 5, Funny

    'bytecode optimized polymorphic inline cache'.

    --
    Sig this!
    1. Re:Mmm... by Anonymous Coward · · Score: 0

      You do realise that shit like this is the male version of "Pro vitamine B5" in shampoo...

  8. Really interesting work by Tragek · · Score: 2, Insightful

    I really am loving this JS engine war; I don't program JavaScript, and know nothing about JIT, but having read more than my fair share of compiler optimization and analysis papers, it's really good to see that compiler tech and research is alive and kicking.

    1. Re:Really interesting work by mdmkolbe · · Score: 4, Informative

      Yeah, except that it's JavaScript, traditionally one of the slower languages because it's objects are basically hashtables. The improvements you see are going to be mostly to fastpathing past those hashtables. This unfortunately means that the improvements you see in JavaScript are unlikely to port to other languages since those improvements are to a feature that isn't used in most other languages. (Lua and Python may be exceptions.)

    2. Re:Really interesting work by Spy+der+Mann · · Score: 2, Insightful

      Yeah, except that it's JavaScript, traditionally one of the slower languages because it's objects are basically hashtables.

      And php stores its variables.... how?

    3. Re:Really interesting work by dgatwood · · Score: 2, Insightful

      And Perl stores its classes how?

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    4. Re:Really interesting work by Tragek · · Score: 1

      As near as I can tell, most of what's being done in SquirrelFish, V8, etc is not new; Most of it was pioneered in the Java JITs. It's just interesting to see this applied to other languages

    5. Re:Really interesting work by catch23 · · Score: 1

      Actually the work can be ported to many other dynamic languages, ruby, python, basically the "hot" dynamic languages on the market today will find uses for this. Some ruby implementations like JRuby have a monomorphic inline cache, which is just a few steps behind from being able to handle multiple class hierarchies.

    6. Re:Really interesting work by catch23 · · Score: 1

      Hah, and you think the work there was new? Lots of this was done in the smalltalk before it was done in Java VM's JIT. Actually tons of implementation these days are old ideas updated to new languages. Wait 20 years and you'll see these same technologies reimplemented in a different language.

    7. Re:Really interesting work by giuntag · · Score: 1

      That was about the first question that came to my mind: are the Python/Parrot/PHP/Ruby guys aware of these developments in js technology? Are they already porting the techniques? Or is it impossible to take advantage of them because of the basic assumptions in the underlying VMs?
      After all, despite all these languages interpreters being mature enough (erm, maybe the P ones...), javascript engines are seeing a tremendous advance in speed after many years of relative stagnation...

    8. Re:Really interesting work by Anonymous Coward · · Score: 0

      If these techniques only end up being applicable to JavaScript, Lua, Python, Perl and Ruby, then... well... I think that's still pretty good.

    9. Re:Really interesting work by Anonymous Coward · · Score: 1, Insightful

      The reason the current crop of dynamic languages are slow is not technology, it's lack of manpower and/or willingness. Smalltalk and Lisp implementations were tuned into damn fast interactive compilers (which is not quite the same thing as JIT) back in the 1970's and 80's when Smalltalk and Lisp were relatively popular and they had multiple competing commercial vendors.

      However popular python, perl and php are, there simply doesn't seem to be sufficient interest to develop a fast dynamic compiler and make it fully supported. There have been multiple projects to make smart python compilers, but the mainstream python implementation community stays behind the slow interpreter which is where all the language and library development happens. Thus the python compilers (ShedSkin, PyPy, IronPython and whatever else there is) have fallen behind and never managed to get to production level.

      Then there is the parrot JIT virtual machine project for perl, which may actually get finished any decade now. I don't know if it's manpower they lack, or if it's the second-system effect in action. As for PHP, I haven't followed developments there.

      Javascript is an interesting case - it has become mainstream enough that there is sufficient commercial interest to make the main implementations JIT compilers. Perhaps the important difference to perl and python is that Javascript is defined by workable (although not perfect) standards and there are multiple competing implementations instead of a single interpreter. Or maybe it was just a question of sufficient need and funding producing the required push and manpower.

      Whatever the reasons javascript is making the transition, I don't see perl, python or PHP in the same position to take advantage of them. All of the latter are still defined by a single major interpreter implementation, and don't have the kind of backing javascript has.

  9. Javascript by Lord+Byron+II · · Score: 4, Interesting

    You know, 5 years ago, if somebody had asked me about Javascript, I would have told them that it was a dying technology. At the time, it seemed that it was only used for pop-ups and advertisements. Back then, I had it turned off in all of my browsers. Now, we rate browsers based on their Javascript performance... amazing.

    1. Re:Javascript by MightyYar · · Score: 3, Insightful

      it seemed that it was only used for pop-ups and advertisements.

      No, no... it was also used to invade your privacy.

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
    2. Re:Javascript by PietjeJantje · · Score: 5, Interesting

      I would go a little further than that, realizing this is difficult to swallow for many following the javascript/ajax bashing meme here on Slashdot for so long, but in their desire to snub it as something "real" software engineers wouldn't touch (or is it fear of change from an aging community?) the clear reality IMHO is that javascript is taking over the role on the client side that java was supposed to be, and it is to be the platform for Google and such to compete against MS on the desktop. You can choose to ignore that, but I doubt it's a good career move, especially considering some of the powers behind it, pushing the technology. Kids today, where they used to make MS apps, they now make apps for the browser. MS is shitting its pants by hanging on to a non auto-update of IE6, while IE8 seemingly will sabotage canvas and whatever it can target. They can't keep behind forever with IE6, so it seems the strategy with IE8 will be to battle all that with Silverlight, working best on IE8 of course, to keep the audience on the MS world. I wouldn't underestimate them either whatever you think of that strategy, for the mere fact 25% still use IE6 and seem to be in their hands to start with.

    3. Re:Javascript by Spy+der+Mann · · Score: 1

      it seemed that it was only used for pop-ups and advertisements.

      No, no... it was also used to invade your privacy.

      was???

    4. Re:Javascript by galego · · Score: 1

      exactly ... *was* ... **is** ... and will be able to do so even faster now. ... and the organized crime folk probably didn't even have to fork over a penny.

      --

      Que Deus te de em dobro o que me desejas

      [May God give you double that which you wish for me]

    5. Re:Javascript by Have+Blue · · Score: 1

      It's even more ironic that you have Microsoft to thank for that. They were the ones who originally came up with the XMLHTTPRequest object that made interactive Javascript applications actually useful.

    6. Re:Javascript by Anonymous Coward · · Score: 0

      You know, 5 years ago, if somebody had asked me about Javascript, I would have told them that it was a dying technology

      So, you were completely wrong 5 years ago and now we're supposed to think that what you have to say today means anything?

    7. Re:Javascript by centuren · · Score: 1

      I generally recommend ignoring web development as a career move for programmers who have the skill set to work elsewhere. Being a competent web developer is sort of like being a waiter at a 4-star restaurant. You have to have the talent/experience to get the good job, and you earn a much better salary than other waiters, but in the end, you're still in a field that any high schooler with no formal education can do.

    8. Re:Javascript by multipartmixed · · Score: 1

      You know, I'm a developer with talent and I keep getting stuck fixing crap high schoolers with no formal education THOUGHT they could do.

      *grumble*

      I really don't like web development, I have better things to be doing, but some of this new crap (think Gmail) really DOES need real programmers.

      --

      Do daemons dream of electric sleep()?
    9. Re:Javascript by PietjeJantje · · Score: 1

      It depends on who you're dealing with, but I think you're right for some ;) I've been a web developer for over 10 years, and you have to compete with the local kid with frontpage, with a pool of cheap talent from India, and with the self-educated. That wouldn't be so bad if most your customers and employers would have a clue what's good and what's not - and they usually just go for price. But if you move away from that market/level, it's just like an environment you'd propose. For example, if you'd hack javascript for google, you won't be competing with the frontpage kid. Me, I'm self-employed and got myself a great little niche which combines my own projects/apps and a few projects for customers who are exactly looking for quality. Doubt if the grass is much greener elsewhere. As a kid, I wanted to create games, if I would be a kid a few years back I would probably want to work for Google - look at it now and both careers look boring and neither look good.

    10. Re:Javascript by centuren · · Score: 2, Funny

      Oh, definitely. I deal more with people in their mid-to-late-20s who have chosen web development as a career, and are unable to write professional code, do any sort of documentation, and in some cases even think abstractly.

      This comic quite seriously is almost exactly how the code reviews I give go. I think I use the word "retarded" a lot, also, preceded by "This is the most" and followed by "thing I've ever seen."

    11. Re:Javascript by multipartmixed · · Score: 2, Interesting

      Thanks for sharing that comic. It is *so* true.

      I recently took over a large body web code from another developer. In order to meet deadlines, I'm working nights and weekends (oh, man, I SO THOUGHT I'd left that behind with my 20s). Needless to say, I'm not happy. To make matters worse, I got pulled off a fun project to work on web shit. With a PHP back end.

      So, anyhow.. my kid comes up to me the other day and says, "Boy... you sure swear a lot when you're working!"

      And 99% of my swearing is .. you guessed it. WTF?!?!?!?!!!

      --

      Do daemons dream of electric sleep()?
    12. Re:Javascript by RAMMS+EIN · · Score: 5, Interesting

      ``I would go a little further than that, realizing this is difficult to swallow for many following the javascript/ajax bashing meme here on Slashdot for so long, but in their desire to snub it as something "real" software engineers wouldn't touch (or is it fear of change from an aging community?) the clear reality IMHO is that javascript is taking over the role on the client side that java was supposed to be,''

      Speaking as someone who isn't entirely happy with the direction JavaScripts have taken since the invention of the term "AJAX", perhaps I can shed some light on that. I can't speak for the entire "aging community", but there are bound to be some people who agree with my opinions.

      First of all, calling AJAX bashing a meme is somewhat misleading. I did not speak out against it because it was a meme, I spoke out against it because I had actual technical and philosophical objections. Some of that is emotional: I resent the hype around AJAX. It wasn't actually new; I have been doing stuff like that since 1997 or thereabouts. Where's my recognition? But, the grumpiness of an old man aside, let's look at the technical aspects.

      Many modern, cool websites try to use JavaScript, HTML, CSS, and HTTP to create user interfaces that resemble those of desktop applications. These web technologies were meant to support a request-response model, where each response is essentially a static page. Using JavaScript and CSS, developers create the illusion that it isn't a static page, but a dynamic environment with windows, buttons, menus, popups, anymation, smooth transitions, interaction, etc. In other words, an environment that is nothing like how the web used to be. To support this illusion, heaps of JavaScript are piled on disfigured HTML, and HTTP requests are abused to send what should be small pieces of data to and from the server.

      In the process, compatibility is thrown out of the window - don't try to view any of those pages with an unsupported browser, and don't try to analyze the page with a web spider; you will only end up with garbage. Even if you have a supported browser, you will need a pretty powerful computer to get anywhere near decent responsiveness from what are really very primitive user interfaces. This is why I have opposed the wave of AJAX websites. It's not that I don't think the things that are being built with it aren't cool. But they are being built on the wrong technology, which yields suboptimal results and, at the same time, inhibits the adoption of what would be the right technologies. I am happy to see fancy interactive applications being built on open standards, rather than on proprietary technology, but I would rather have it be built on standards that were designed for it, rather than breaking existing standards to get something that sort of works, if you have a fast computer and the right browser. And yes, I do regard any HTML that can't be usefully processed by a search engine or screen reader as broken.

      All this is is nothing against JavaScript. I think JavaScript is a nice language, and I am happy to see we're finally working on creating implementations that aren't dog slow. Perhaps we can also add some useful features...for example, raw sockets, so that we don't have to occur the overhead of a full HTTP request any time we wish to communicate with another system. And perhaps we could actually standardize APIs to functionality like native widgets (how is XUL these days?) and drawing functions (something like Cairo, perhaps?). Then we would have a platform that is actually good for interactive applications. Throw in some support for libraries (with caching and versioning) so that not everything needs to be reloaded all the time, and it's starting to look like a very workable solution.

      You see, I am not opposed to change ... I am opposed to changing in a direction we know isn't very good, when we know how to make it better.

      --
      Please correct me if I got my facts wrong.
    13. Re:Javascript by PietjeJantje · · Score: 3, Interesting

      In the process, compatibility is thrown out of the window - don't try to view any of those pages with an unsupported browser, and don't try to analyze the page with a web spider; you will only end up with garbage. Even if you have a supported browser, you will need a pretty powerful computer to get anywhere near decent responsiveness from what are really very primitive user interfaces. This is why I have opposed the wave of AJAX websites.

      While there's substance to most of your arguments, you -are- getting old, I'm afraid. It reminds me of times when one was flamed for using C over assembly. It reminds me of the time when I was a student and Mosaic 0.9b was released, and it was a non-event because of the above sentiment: slow, resource hungry, and in a time when it was undone to send sigs over 4 lines not regarded a good thing.

      In the meantime the world will move on, javascript already got great cross-browser libraries that make sure it works from IE6 to webkit, and data exchange will be unhyped and improve over time. But no, you can no longer view it on Lynx, and the web -will- be expanded from the dom/request&response model to a dom+javascript (the natural companion) model with more sophisticated means of data exchange. It's a development the noscript-ers can forget they can stop it. It's not like accessibility is not important though, this is an area of development and research as well. Google wants to be able to index that. Also, it's not a xor situation. Google's search pages work on everything. For their apps you need javascript. It's just an extra option (sure it's abused for badly degradating bling - but the web will always be 99% pulp). On the interface site I don't expects any standards soon, but the improvements of the APIs of the big players are big from version to version.

      I think you'll be surprised how good and smoothly it will work and already can work if you look for the right examples. It's easy to have formed an opinion on this stuff a while back and freeze it (especially as you can always choose and pick from millions of examples of bad implementations or use), and mine would have been roughly the same. First of all, I'm a nut for graceful degradation. And I hate those first gen web office apps, all with their scruffy custom interfaces, endless ajax loading indicators, curvy orange and cyan "look how cool I am" cliches involving the marketing term web 2.0, and in general wanabee behavior which makes you think "why? WHY on earth do it in the browser", and "oh noo, not reinvent the wheel again by taking steps backwards". Forget that. It's moving on, and soon all your objections will be as relevant as someone who says you should use assembler over C or even C over Python.

    14. Re:Javascript by multipartmixed · · Score: 1

      Too bad they didn't copy navigator's DIV.src property.

      That would have been even more useful with readyState added.

      I used to use it back in the day by ending each dynamically-loaded DIV with a hunk of javascript that triggered a call back.

      And DIV.src makes AHAH easier. Well, marginally. Support for HTML OBJECTs would do the trick as well.

      --

      Do daemons dream of electric sleep()?
  10. Message to Google by Anonymous Coward · · Score: 0

    An old question not entirely on-topic.

    Can we try to update HTTP/HTML/JavaScript/Cookie paradigm to better accommodate web applications? All these improvements are great, but despite the improvement, some quite impressive technically, it all only adds up to minor incremental and inefficient improvements. Not to mention now that we have cell phones devices to accommodate.

    If anyone has clout and interest in this, it'd be Google. I'm sick of responding to dialog boxes from cookie setting, noScript, etc.

    Well, enough of that, time for me to get onto more serious drinking.

    1. Re:Message to Google by Anonymous Coward · · Score: 0

      > Well, enough of that, time for me to get onto more serious drinking.

      http://99-bottles-of-beer.net/language-javascript-1079.html ?

    2. Re:Message to Google by MightyYar · · Score: 0, Offtopic

      Well, enough of that, time for me to get onto more serious drinking.

      You know what commitment is? The only bottle of red wine left in the house is one of those big 1.5 liter mothers. You know what? I fuckin' opened it anyway and I'm only about halfway through.

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
    3. Re:Message to Google by Darkness404 · · Score: 3, Interesting

      If anyone has clout and interest in this, it'd be Google. I'm sick of responding to dialog boxes from cookie setting, noScript, etc.

      Simple answer. Stop being so paranoid. Just allow all first-party cookies, have a decent /etc/hosts file that blocks ads and use Linux/OS X/Any OS other than Windows and you are basically safe from any major malware outbreak. I've tried noScript and found it to be more of a pain then it was worth. Sure, it might make you less secure, but honestly, I run Linux and even though it is possible to hack a Linux box, most script kiddies won't bother.

      Google doesn't care about you, the .01% of the internet that doesn't just accept scripts and cookies.

      --
      Taxation is legalized theft, no more, no less.
    4. Re:Message to Google by neokushan · · Score: 1

      What exactly has windows got to do with browser vulnerabilities (aside from IE, of course)?

      --
      +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
    5. Re:Message to Google by Darkness404 · · Score: 0, Flamebait

      Because a lot of browser vulnerabilities either inject platform specific code or download a binary. If the binary isn't made for Linux nothing happens. If the code doesn't run on Linux then again, nothing happens. Also, most Linux users know that something is wrong when they have a browser toolbar they didn't install, on the other hand Windows users are used to MS forcing updates after updates at them and think that it is perfectly natural that their homepage is hijacked to some ad website and they have 10 popups every hour and they have 3 browser toolbars they never installed. The Windows way teaches people they don't own their computers and so they are naturally less aware of changes whereas with Linux (or any other non-Windows platform) something got changed the average person would at least look into it somewhat.

      --
      Taxation is legalized theft, no more, no less.
    6. Re:Message to Google by neokushan · · Score: 2, Insightful

      That's a very good...pile of FUD right there.

      Lets see here, you're pretty much saying that if you use Linux, you'll simply KNOW when something is up with your system, but if you use windows, you wont because you'll think it's just some sort of update Microsoft is pushing on you? What about the average Mac user, do you honestly think they're "Technically-inclined" when the entire marketing campaign Apple uses can be summed up as "Buy a Mac - because it'll make you cool"? Or what about all those people who just bought an Eee PC (or similar) because they're affordable and all the rage? Will they suddenly become experts overnight and know the ins/outs of linux, at least enough to know when it's doing something it's not supposed to?
      Besides, when was the last time you seen Windows Update automatically install a new toolbar or whatever? The only thing I can think of in recent memory was the new Live search thing and I'm sure that was an OPTIONAL download anyway (and anyone that just ticks all the boxes and downloads anything they see without reading about what they're getting is just asking for trouble). Even IE7 is optional. Everything else is just security/program updates, with the exception of the odd service pack (which is what, once every 2 years?).
      Plus, it's not like modern Linux distributions don't have their own update programs within them, particularly those designed for the novice user. How are they going to know that their fancy new toolbar isn't just something linux has?

      Your advice to the above poster is possibly the worst advice you could ever give anyone - "Use this OS and you'll be safe!". That's a load of bull, it just takes one person to make a virus and/or Trojan targeting that OS and your complacency will be taken complete advantage of because "you're running linux - YOU'RE SAFE!". The best way to ensure your system doesn't get compromised is to be careful and vigilant, which is exactly what the OP is, then even the "few" script kiddies that actually do target you will be hard pushed to hax0r your b0x0r.
      Yes, it's a minor inconvenience, but it's the ONLY way to be absolutely sure you're safe. And yes, this even works on WINDOWS boxes. Shocking, I know.

      I hate defending Microsoft, but I hate it even more when people bash them for all the wrong reasons, or use feeble excuses - at least have a go at them for something genuine, it's not like you haven't got much to pick at them with.

      --
      +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
    7. Re:Message to Google by Spy+der+Mann · · Score: 4, Insightful

      Your advice to the above poster is possibly the worst advice you could ever give anyone - "Use this OS and you'll be safe!". That's a load of bull, it just takes one person to make a virus and/or Trojan targeting that OS and your complacency will be taken complete advantage of because "you're running linux - YOU'RE SAFE!".

      Hmmm... right, and wrong.

      You (and also the GP poster) have fallen for the "Linux isn't hacked because it's not the majority" straw-man. Linux is much harder to hack because it provides a much better security than Windows. For starters, you can run your software as non-root! And for any installation you actually have to provide a password. Compared to the Vista "Cancel, Allow" prompts, this is much better, because people unconsciously hit allow because they get trained (by Vista) to do that. Also, GNU/Linux does not have unknown services enabled by default.

      Also, when the GP says that Linux users know something's wrong because they have an extra toolbar, he's right. If I have an extra toolbar on Firefox that I didn't install, i'm not just in trouble. I'm in DEEP trouble and I can almost guarantee that someone pwned my PC (or at least my user account). This is a question of knowledge, granted, but Windows users who have NO IDEA of what's going on inside their OS, just say "oh well, I'll just have to get accustomed to it". And the worst part: they DO get accustomed to it! It's like the battered wife syndrome, but with viruses.

      Also, Microsoft products are prone to have security holes because their software is not open source (many eyes make bugs shallow). Open Source software gets updated almost the day after when a vulnerability is discovered.

      Finally, MS products are also prone to have security holes because since the old MS Word days they keep mixing data with code. First there were the Word Viruses, then the Excel Viruses, then the e-mail viruses, and thanks to ActiveX, webpage viruses. And if that wasn't enough, we got WMV viruses, MP3 viruses (which are possible thanks to stupid security policies like not warning you when the filetype is actually different than the extension reported), and don't get me started with autorun.inf viruses in USB drives.

      They never learn!

      So, yes, GNU/Linux is more secure per-se than Microsoft Windows. That's a FACT. And yes, it's also more secure because GNU/Linux users are more careful.

    8. Re:Message to Google by neokushan · · Score: 1

      I never once said that Linux is just as easy to attack as Windows. I also never said that it's security had anything to do with it's overall marketshare, what I said was that if you believe you're secure BECAUSE you're using Linux, then you're just as vulnerable to attack. True, the chances of some random exploit being a problem are severely reduced, but it's not like a clever kiddie couldn't produce different attack code depending on what the User Agent of your browser reports.
      I also (briefly, perhaps I brushed over this one a bit too much) tried to point out that a Vulnerability in the browser has little to nothing to do with the OS it's running on. If Firefox is open to attack, it's open to attack no matter if it's running on Linux, Mac OS X or Windows (with a few exceptions here and there, of course).

      Basically, the sum-total of my argument is "don't blame windows". Anyone that's using linux and knows what they're doing enough to know when something is wrong can also safely secure a Windows box. It's not rocket science, it's mostly just common sense and applies to just any OS.
      "I'm a PC" (couldn't resist) and I know that if a mysterious toolbar appears, something is dreadfully wrong. Thankfully, that hasn't happened in a while. See, it doesn't just apply to Linux users, it applies to any experienced user.
      At least if a big exploit comes out, the OP will be safe, but if he just "switched" to Linux and left it at that, he'd still be open to attack. And what if the attack was more malicious than simply installing a toolbar? What if it was less-obvious? Surely thinking "I'm ok, I'm not running windows!" is just going to make the situation worse?

      --
      +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
    9. Re:Message to Google by x2A · · Score: 0, Offtopic

      haha, cheers!

      I visited my parents today for a younger brother's birthday, and found a bottle of red they'd bought at 14.5% alc... I was so proud of 'em :-)

      --
      The revolution will not be televised... but it will have a page on Wikipedia
    10. Re:Message to Google by x2A · · Score: 1

      "If the binary isn't made for Linux nothing happens"

      Yeah right! My linux machine got infected with a virus and it took forever cuz it was over 50meg download cuz it needed it installed WINE first. I wouldn't mind so much but I was connected on my 3G card, phone bill at end of the month was *massive*. At least windows can run viruses natively so they don't have to be statically linked to libwine. That saves me loads of money when I'm connected thru my mobile phone.

      --
      The revolution will not be televised... but it will have a page on Wikipedia
    11. Re:Message to Google by Spy+der+Mann · · Score: 1

      What if it was less-obvious? Surely thinking "I'm ok, I'm not running windows!" is just going to make the situation worse?

      You're absolutely right. Security is not a product, it's a process. This is why I keep browsing slashdot and tech sites to make sure my software doesn't have a hidden vulnerability around.

    12. Re:Message to Google by centuren · · Score: 1

      Easier answer: have your browser block all cookies, adding exceptions for the 20 websites you need them from (and can list off the top of your head).

    13. Re:Message to Google by Fizzl · · Score: 1

      wat

    14. Re:Message to Google by neokushan · · Score: 1

      Point-in-case: Being vigilant is the answer, not running a certain piece of software (or rather, not-not running a certain piece of software).

      --
      +1 IDisagreeSoHeMustBeATrollOrAnAstroturferOrAShill
    15. Re:Message to Google by Spy+der+Mann · · Score: 1

      Point-in-case: Being vigilant is the answer, not running a certain piece of software (or rather, not-not running a certain piece of software).

      Yes, but usually being vigilant implies not running a certain piece of software ;-)

    16. Re:Message to Google by Anonymous Coward · · Score: 0

      You (and also the GP poster) have fallen for the "Linux isn't hacked because it's not the majority" straw-man.

      Nice straw-man! No, it's the security through obscurity argument, which is a valid argument. Worms and such have been written for Unix as a proof of concept. Rather humorously, there was even the de-penguinator some years back, that converted Debian systems to FreeBSD systems. Linux just isn't an appealing platform for malware developers simply because nobody uses it (relatively speaking). If you're building a botnet, for example, do you go after the platform that has 0.93% of the market, 8% of the market, or 91% of the market. And then there's the issue of Linux getting nowhere near the level of exposure as Windows does.

      For starters, you can run your software as non-root!

      It's called not running as an administrator. Administrator rights are required for editing system files and installing software, which is the same case as on Linux, except one uses su and sudo, the other used 'run as'. I've always disliked sudo in that it authenticates against the user's password, defeating the purpose of having a separate superuser account. If the sudoer account gets compromised, the intruder has root access.

      And for any installation you actually have to provide a password.

      using 'run as' as a normal user in XP requires the admin password to run as admin. Very much the same as using 'su' in Unix. But it's a cute strawman here, comparing running as an administrator to running as not-root. Linux doesn't prompt you for a password if you're already authenticated as the superuser either.

      Also, Microsoft products are prone to have security holes because their software is not open source (many eyes make bugs shallow). Open Source software gets updated almost the day after when a vulnerability is discovered.

      I've always hated this argument, since it implies that somehow open source applications are magically less prone to security holes (like shipping sshd with the random number generator disabled, that could never happen, could it?) by virtue of being open source.

      First, we'll compare the amount of Secunia advisories for Linux 2.6.x (open) and AIX 6.x (proprietary):

      Linux:
      Vendor: Kernel.org
      Affected By: 154 Secunia advisories 273 Vulnerabilities
      Unpatched: 6% (10 of 154 Secunia advisories)

      Aix:
      Vendor: IBM
      Affected By: 14 Secunia advisories 47 Vulnerabilities
      Unpatched 0% (0 of 14 Secunia advisories)

      How can this be? I proprietary OS has not only viewer overall vulnerabilities but less unpatched ones as well? But it's proprietary, it's prone to security holes!

      For shits and giggles, we'll throw in Windows Vista and Server 2003 Standard, both of which are proprietary and have better track records. And yes, I do realize that I'm stacking the deck in Linux's favour by comparing full proprietary operating systems to a single component of Linux (the kernel).

      Vista:
      Vendor: Microsoft
      Affected By: 40 Secunia advisories 63 Vulnerabilities
      Unpatched: 8% (3 of 40 Secunia advisories)

      Windows Server 2003 Standard Edition:
      Vendor: Microsoft
      Affected By: 15 Secunia advisories 27 Vulnerabilities
      Unpatched: 7% (1 of 15 Secunia advisories)

      I'm also aware that comparing known vulnerabilities is a shitty yardstick, but the number of vulnerabilities is much less important than the amount of known vulnerabilities left unpatched.

      Secondly, all software is prone to bugs and security vulnerabilities, regardless of the availability of source code.

      Third, whereas the million eyes rhetoric does work, ideally, in the mirror universe populated entirely by skilled programmers (with goatees, of course), it assumes that everyone knows what they're doing and ignores that source code is absolutely useless in the hands of someone who doesn't know what to do with it. It also implies that proprietary code is

  11. Could someone please.. by DanWS6 · · Score: 1

    Show me an example of a website with so much javascript that it is too slow to use? I really don't know of any sites that bring Mozilla to a crawl, most of those are flash or java applets.

    1. Re:Could someone please.. by hostguy2004 · · Score: 1

      Yeah, Slashdot - Try viewing a story with 500 comments!

      --
      In Soviet Russia ^H^H^H America, The bank finances YOU!
    2. Re:Could someone please.. by davidpack01 · · Score: 0

      Ever since Digg redesigned their comments page it has ran like a dog on my system, but Digg is so awful nowadays that it really doesn't matter.

    3. Re:Could someone please.. by bunratty · · Score: 4, Informative

      There are very few popular sites that are too slow, because web developers do not like to make slow sites. If a web developer does make a slow site, it doesn't become popular because users are too impatient and go to faster ones.

      That's really the whole point of the recent focus on JavaScript performance. Web developers want to make complex sites to support the features the users want, but they cannot because all those features make the sites too slow. Google especially wants to develop a web-based Office-killer suite. That's why they developed Chrome with a very fast JavaScript engine, minimal chrome to make web apps more like local apps, and put each tab in a separate process so you can kill those memory- and CPU-hungry sites when you need to.

      --
      What a fool believes, he sees, no wise man has the power to reason away.
    4. Re:Could someone please.. by DrEldarion · · Score: 1

      Not too slow to use normally, but try using a Google spreadsheet in Firefox and then switch over and use it in Chrome. The different in speed when it comes to web applications is pretty astounding.

    5. Re:Could someone please.. by cheater512 · · Score: 1

      Slashdot + GMail plus a compile or two on 512mb ram does the trick. ;)
      Real life scenario. Thats what I'm doing right now.

      Speed for the sake of speed isnt bad anyway.
      I dunno about you but I like zippy computing experiences.

    6. Re:Could someone please.. by MightyYar · · Score: 1

      Show me an example of a website with so much javascript that it is too slow to use?

      280 Slides. It won't bring Mozilla to a crawl, but it is noticeably faster on Chrome. IE is almost unusable.

      I'm actually excited about sites like this - web apps could really go somewhere if they were all this feature-rich.

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
    7. Re:Could someone please.. by Anonymous Coward · · Score: 0

      280 Slides is basically a slower version of Keynote with 95% of the features removed. I really don't see the attraction of running things like this in a web browser.

    8. Re:Could someone please.. by Anonymous Coward · · Score: 0

      Facebook severely slows down every browser I've tried on it. That happens even when I've got Flash disabled, so I'm pretty sure it's the javascript.

    9. Re:Could someone please.. by Anonymous Coward · · Score: 0
    10. Re:Could someone please.. by Spy+der+Mann · · Score: 1

      Yeah, Slashdot

        - Try viewing a story with 500 comments!

      I was gonna mention Digg, but your example really made me laugh. But yes, Digg is a royal pain in the ***, specially when you hit "expand all". Sheesh... I've had to close Firefox more than once because the digg comments take AGES to load. So, DanWS6, there's your example of a painfully slow javascript-based website.

    11. Re:Could someone please.. by jesser · · Score: 1

      Slashdot + GMail plus a compile or two

      I hope you're not using your web browser to compile C++ applications ;)

      --
      The shareholder is always right.
    12. Re:Could someone please.. by cheater512 · · Score: 1

      Err shouldnt I be? :P

    13. Re:Could someone please.. by Logic+and+Reason · · Score: 1

      You know, you can get 2GB of desktop RAM for about $40 these days. Laptop memory and older kinds of desktop RAM are more, but not by much.

      Seriously, you're not doing yourself any favors by using a machine with half a gig, even if you're running some bare-bones Linux distro. Join us here in 2008!

    14. Re:Could someone please.. by justcauseisjustthat · · Score: 1

      You're missing the big picture. Javascript & browsers are the basis for cross platform compatible applications, that due to the newer abilities to run those application when offline will compete with MS Office. Faster the Javascript, faster the application, yummy.

    15. Re:Could someone please.. by cheater512 · · Score: 1

      $65 for a 1gig stick of DDR in Australia? No thanks.

      I dont actually need more ram. I get by on 512 fine.
      KDE 4.1 helps a lot fyi.

    16. Re:Could someone please.. by Yetihehe · · Score: 1

      Just wait till I end my project in about a month. It should be really done in flash, but REALLY it should be never done. To top it off, it will work on a server which is slower and smaller than my desktop.

      --
      Extreme Programming - Redundant Array of Inexpensive Developers
    17. Re:Could someone please.. by FooBarWidget · · Score: 1

      "If a web developer does make a slow site, it doesn't become popular because users are too impatient and go to faster ones."

      Hahaha! Check again: hyves.nl. One of the most popular sites in the Netherlands. Contains tons of unnecessary Ajax affects and very, very slow.

    18. Re:Could someone please.. by MightyYar · · Score: 1

      For me, the attraction is:
      1. I can sit down at any computer anywhere and access my file.
      2. No software installation on my 3 computers.
      3. Sharing with other people does not require that they have my presentation software, or some lame conversion to PDF.

      If performance were high enough, then features could be added.

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
  12. Re:Tracemonkey is slower than V8?, controls the ou by martinw89 · · Score: 1

    He who controls the test suite

    Err, Google doesn't control or own the test suite. I wasn't talking about Apple either.

  13. Re:Tracemonkey is slower than V8?, controls the ou by Anonymous Coward · · Score: 0

    No, but they get to choose which test suite they use and post benchmarks from.

  14. Sure, now with anecdotal evidence! by martinw89 · · Score: 4, Interesting

    I have Opera 9.5 and FF 3 on my Ubuntu system. There is a noticeable difference in rendering speeds for JS medium-heavy websites between them, Opera being slower. Now, I had no idea of Opera's relative speed when I noticed this. So I tested them with Sunspider and surely enough there was a good gap between both, with FF 3 being much faster in benchmarks.

    NB: I'm not being anti Opera. Opera is awesome, even though it's not my primary browser. I'm just saying you can notice the difference in slower JS engines.

  15. Picture of a G5 Processor? by pizzach · · Score: 5, Informative

    Why? Does apple even sell those anymore?

    --
    Once you start despising the jerks, you become one.
    1. Re:Picture of a G5 Processor? by alvinrod · · Score: 1

      And Bill Gates still shows up for MS stories and he's retired. Granted he's doing commercials now, but that's about it.

      They're kind of iconic and nostalgic in a way. Sure it's only been a few years/weeks, but in the tech world that may as well be eons.

      Besides, the editors can't even be bothered to spell check story summaries or make sure they're factual. What makes you think they'll take the time to update the story icons?

    2. Re:Picture of a G5 Processor? by hansamurai · · Score: 2, Interesting

      Not to mention the cup of coffee with the alt tag "Java" representing a javascript story.

    3. Re:Picture of a G5 Processor? by pizzach · · Score: 1

      It would be interesting if the borg-gates image was changed to an animated gif of his shaking ass. At least it would be more up to date then.

      --
      Once you start despising the jerks, you become one.
  16. Small test by Anonymous Coward · · Score: 1, Insightful

    Have a webapp that uses Extjs, and does some pretty hefty DOM manipulation. A small test on it just now, and firefox 3 still smokes the latest webkit on it by a very wide margin.

    1. Re:Small test by Anonymous Coward · · Score: 0

      Care to post the benchmark?

    2. Re:Small test by BZ · · Score: 2, Informative

      Yep. Sunspider is a pure JS benchmark, no DOM.

      By the way, expect Firefox 3.1 to have faster DOM access than Firefox 3. It's being pretty actively worked on.

  17. Open standards, healthy competition, free software by Anonymous Coward · · Score: 0, Funny

    I never quite got how its a wonderful thing when Apple and Google cross-subsidize free-as-in-beer Internet browsers but when They Who Must Not Be Named do the same thing its evil, monopolistic, anti-consumer behavior.

  18. It may not change the browsing experience.. by Anonymous Coward · · Score: 0

    Your javascript has got to run at a decent speed on all browsers. So given the fact that the slowest javascript interpreter in wide use is by a magnitude slower, I really doubt we'll see any really nifty applications any time soon; it will however take embed systems one step closer to their desktop counterpart.

  19. Speed of JS engine matters why? by taloobie · · Score: 1

    This whole "who's fastest" is just like the chip wars. No real user understands this jive. Worse, just like the CPU, the speed of the JS engine is usually not the limiting factor in the User Experience. Design, Function, Server Response, Ad Calls... those all typically are what retard the user experience. If you work for clients like I do, we have to prepare for LCD not the slashdot guy who installs things in pre-release phases. Who Cares?!

    1. Re:Speed of JS engine matters why? by bunratty · · Score: 4, Insightful

      For the next generation webapps that web developers haven't been able to write because JavaScript has been too slow until recently.

      --
      What a fool believes, he sees, no wise man has the power to reason away.
    2. Re:Speed of JS engine matters why? by MightyYar · · Score: 0, Offtopic

      No real user understands this jive.

      You have a lower ID than me - why do I have to explain that you are at the "news for nerds" site and not Fox News :)

      --
      W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
    3. Re:Speed of JS engine matters why? by Darkness404 · · Score: 1

      This whole "who's fastest" is just like the chip wars. No real user understands this jive.

      No, but this means that marketshare for IE will almost certainly go down and that is only a good thing. It also means that Firefox marketshare will go down which is also a good thing because competition always helps in open source projects and Firefox can't just be the only F/OSS browser that renders pages decently.

      Worse, just like the CPU, the speed of the JS engine is usually not the limiting factor in the User Experience. Design, Function, Server Response, Ad Calls... those all typically are what retard the user experience.

      Sure it isn't the limiting factor, but if it makes interactive web applications run faster it can help pave the way for the end of annoying Flash navigation (and thus the end of 99% CPU usage on non-Windows platforms) and help build standards.

      --
      Taxation is legalized theft, no more, no less.
    4. Re:Speed of JS engine matters why? by Yetihehe · · Score: 1

      Long live javascript realtime raytracing games!

      --
      Extreme Programming - Redundant Array of Inexpensive Developers
    5. Re:Speed of JS engine matters why? by Anonymous Coward · · Score: 0

      For the next generation webapps that web developers haven't been able to write because JavaScript has been too slow until recently.

      And still won't be able to write since JavaScript will continue to be slow for 75% of the population.

    6. Re:Speed of JS engine matters why? by taloobie · · Score: 1

      C'mon, that's not why we haven't written the next generation web apps. a) there's been no business model for browser based apps up until now (heck, even now there really isn't one other than a big company can buy you...) b) broadband usage is finally a large enough set of users to justify building these apps c) the entire toolchain wasn't in place (dev tools, REST, native XML output, js libraries) I still don't think the js engine speed itself contributed much at all to the glacial development of next gen web apps. and I agree with others that if we could get away from Flex, Silverlight and all these other non standard, none open, need an expensive dev kit to product methods, we'd all be better off.

  20. Re:Open standards, healthy competition, free softw by Per+Wigren · · Score: 2, Insightful

    The LGPL and BSD licenses are "free as in beer" now?

    --
    My other account has a 3-digit UID.
  21. Re:Open standards, healthy competition, free softw by DrEldarion · · Score: 1

    Well, Google's is entirely open source, for one thing. You can't really make an anti-consumer argument about that.

  22. Re:Open standards, healthy competition, free softw by MightyYar · · Score: 3, Insightful

    I never quite got how its a wonderful thing when Apple and Google cross-subsidize free-as-in-beer Internet browsers but when They Who Must Not Be Named do the same thing its evil, monopolistic, anti-consumer behavior.

    I can understand thinking it's not evil or anti-consumer... but c'mon - monopolistic? It's the very definition! A monopoly isn't illegal - using it to gain an advantage somewhere else is. Apple, with their pathetic little market share is not even close to a monopoly. Even their iPod is only like 70% of the market. Google has a near-monopoly on search - but how they are using that to gain an advantage via a web browser is pretty questionable. It's not like you have to use their browser to search or something - they don't even promote it on their home page.

    --
    W..w..W - Willy Waterloo washes Warren Wiggins who is washing Waldo Woo.
  23. Re:Open standards, healthy competition, free softw by samkass · · Score: 0

    I feel the same way about Android, incidentally. Now you're going to have a cellphone that's completely subsidized by another business in which the company has a virtual monopoly. And they'll be able to link their web content to their cellphone by adopting standards that the competition chooses not to (the nice thing about standards is that there are so many to choose from). They're treading a pretty fine line here, and things like the Mobile Street View working on most phones except the iPhone aren't going the help the anti-trust argument any.

    --
    E pluribus unum
  24. Google... by simplerThanPossible · · Score: 1

    Even when they lose, they win.

    1. Re:Google... by Darkness404 · · Score: 4, Insightful

      Replace Google with any standards-supporting, partially open source vendor and you have the current market situation. Heck, if WebKit manages to somehow run JavaScript at twice the speed of assembly programs, Mozilla can still take that code and make Gecko's JavaScript engine just as fast. If Red Hat releases a tool that can run all Windows applications at full speed on Linux, Novell and Canonical don't lose out, they gain too, in that example even the WINE and ReactOS team could gain something. It is only the proprietary vendors that lose whenever the competition gets a new feature. Only IE and Opera that can't tap into these new JavaScript engines. It helps every open source browser project, from Firefox to Konqueror, to Chrome, to even Safari. It is only the few that remain closed that this will hurt.

      --
      Taxation is legalized theft, no more, no less.
    2. Re:Google... by jesser · · Score: 4, Insightful

      If the license is permissive (like the MIT license), Opera and IE can incorporate the new code just as easily as open-source browsers can. If the license if open-source but not especially permissive (like the GPL), Opera and IE can't use it, but neither can many other open-source projects.

      As it happens, V8 is BSD, Tracemonkey is LGPL+MPL+GPL, and SquirrelFish is LGPL+BSD. I believe BSD and MPL are both permissive enough for use in Opera and IE.

      --
      The shareholder is always right.
    3. Re:Google... by simplerThanPossible · · Score: 1

      Actually, what I meant was that Google benefits from faster javascript in that it makes the web more attractive to more users. More web users means more people clicking on Google advertisements. Whether this happens because of Google's own browser, or because it spurns on the competition, Google wins just the same.

      It's similar situation in that spectrum auction, where Google didn't win (it dropped out, I think), but it managed open up the spectrum.

      Google's interests mostly coincide with the public interest - so far.

  25. Q! by AKAImBatman · · Score: 5, Insightful

    I never quite got how its a wonderful thing when Apple and Google cross-subsidize free-as-in-beer Internet browsers but when They Who Must Not Be Named do the same thing its evil, monopolistic, anti-consumer behavior.

    You know what I can't believe? I can't believe this crap got modded up. Talk about a disingenuous argument if I ever saw one.

    Call me when:

    • Microsoft can meet standards they helped develop. You know, simple things like DOM2.
    • Microsoft shows an actual interest in progress by supporting the WHATWG rather than rolling out Yet Another Proprietary Platform(TM) like Silverlight.
    • Microsoft actually listens to the REAL problems developers are having in their "Open" development process. Best quote I've heard so far? "I tested IE8 the other day and was unable to remove a single [standards support] hack."
    • Microsoft doesn't cram their browser down your throat with artificial desktop integration
    • Microsoft has their source code for IE available for download
    • Microsoft actually accepts patches for their browser

    If Microsoft did even HALF of that you could act all high and mighty. But from where I stand, you're just another Microsoft shill. Be gone!!!

    1. Re:Q! by Anonymous Coward · · Score: 0

      "from where I stand, you're just another Microsoft shill. Be gone!!!" - by AKAImBatman (238306) * on Friday September 19, @09:26PM (#25081171) Homepage

      You're going to have a tough time of that, considering 90% of the world's computer users use Windows based systems (mostly of the stable & solid nature based on the Windows NT-based family (2000/XP/Server2003/VISTA/Server 2008) nowadays. Keep that up, you'll be a lonely guy man!

    2. Re:Q! by AKAImBatman · · Score: 1

      considering 90% of the world's computer users use Windows based systems

      You know what's amazing? Every one of Microsoft's competitors runs on Windows too! Wow! Isn't that cool? I bet you had no idea! </sarcasm>

      mostly of the stable & solid nature based on the Windows NT-based family (2000/XP/Server2003/VISTA/Server 2008

      See, now I know you're astroturfing. That right there is a bit of market-speak designed by someone who knows the psychology of advertising. Very cute using apparent typos to make yourself look like "one of the guys". But riddle me this: Who makes a different class of typo with each Operating System listed? Shouldn't the typos be consistent? And who makes so many typos when listing OSes, only to spell out "Windows NT-based family" rather than using the more succinct "WinNT family"?

      So, Mr. AC. You haven't been posing as dead people lately, have you? Maybe if you took the time to make a good browser you wouldn't need the astroturf campaign.

  26. Re: by bunratty · · Score: 0

    Uh, because Microsoft is a monopoly and Google and Apple are not?

    --
    What a fool believes, he sees, no wise man has the power to reason away.
  27. "V8" is so 90s by Graywolf · · Score: 4, Funny

    Between TraceMonkey and SquirrelFish, "V8" seems so... weird. They better give it s regular, modern name like ThreadMole or SkunkAmoeba.

  28. Re:Open standards, healthy competition, free softw by Bogtha · · Score: 5, Insightful

    I never quite got how its a wonderful thing when Apple and Google cross-subsidize free-as-in-beer Internet browsers but when They Who Must Not Be Named do the same thing its evil, monopolistic, anti-consumer behavior.

    History lesson for people tempted to fall for this troll:

    Once upon a time, people sold browsers just like they sold any other piece of software. Netscape were making money licensing their browser for corporate environments. The web, and consequently its leader, Netscape, threatened Microsoft's desktop monopoly. So Microsoft used all the cash they had from selling desktop operating systems, bought a web browser (defrauding that company in the process) and spent lots of money developing it further. Then they gave it away for free, at a massive loss to themselves, to "cut off Netscape's air supply". Still, that wasn't enough to unseat Netscape, so Microsoft went further and bundled it into their operating system too. Now all of a sudden 95% of the people on the planet had Microsoft's browser whether they liked it or not - and Netscape were basically dead.

    Microsoft were able to eliminate the competition not because they offered a better product, but because they had a dominant position in another market and were willing to dump their product on the market no matter the cost, to put another company out of business. This is not how capitalism is supposed to work. The free market cannot deal with this situation well. The invisible hand is tied behind its invisible back. So in many countries, abusing a monopoly position in this way is illegal. And that's why Microsoft is vilified here - because they acted like bullies, took something dear to geeks, and shat all over it to make money.

    Now that browsers are a commodity, how are Apple and Google harming the browser market with anticompetitive actions? Answer - they aren't. They are actually competing by providing better products. And that's why it's completely different to what Microsoft did.

    --
    Bogtha Bogtha Bogtha
  29. Amazingly, everyone is faster than everyone else by zoips · · Score: 3, Interesting

    Chrome/V8 is faster than Firefox/Tracemonkey. WebKit/SquirrelFish Extreme is faster than Chrome/V8. Firefox/Tracemonkey is faster than Chrome/V8. And around we go, always twirling, twirling, twirling towards freedom.

  30. Re:Amazingly, everyone is faster than everyone els by mdmkolbe · · Score: 1

    Only one way to settle this, a shootout. Spidermokey is already on there. Get the rest of them up. (I'd get V8 up except it's missing command line arguments.)

  31. Re:Open standards, healthy competition, free softw by AKAImBatman · · Score: 1

    An excellent post, sir. I salute you. Mod parent up.

  32. Something is off by Stan+Vassilev · · Score: 1

    According to comparative benchmarks, the new engine is around 35% faster than the V8 engine recently introduced in Google Chrome, and 55% faster than Mozilla's TraceMonkey.

    If you remember, TraceMonkey was benched to be faster than V8, Brendan Eich said: "We win by 1.28x and 1.19x, respectively. Maybe we should rename TraceMonkey "V10" ;-)."

    And now somehow Safari beats TraceMonkey by 20% more than it beats V8. Funny that.

    Those benchmarks are useless.

    1. Re:Something is off by jesser · · Score: 1

      That's not a sign that the benchmarks are useless. That's a sign that V8 has improved since the version that shipped with Chrome.

      --
      The shareholder is always right.
    2. Re:Something is off by BZ · · Score: 1

      You're assuming that "V8" and "Tracemonkey" (and "SFX", for that matter) are frozen entities. They happen to be in active (furious, really) development, so the relative speeds change daily if not more often. Especially if you pick a particular test.

    3. Re:Something is off by Stan+Vassilev · · Score: 1

      They happen to be in active (furious, really) development, so the relative speeds change daily if not more often. Especially if you pick a particular test.

      If I picked a "particular test" it'd be a very useless benchmark, which is what I said originally.

    4. Re:Something is off by BZ · · Score: 1

      I meant a particular subtest of the benchmarks. The better benchmarks aim to have a variety of tests that exercise as much of the engine's functionality as possible.

  33. Re:Open standards, healthy competition, free softw by Spy+der+Mann · · Score: 1

    I second that. You've just been added to my friends list.

  34. no, by toby · · Score: 1

    But plenty of people still use them.

    --
    you had me at #!
  35. The invisible hand is working just fine by SuperKendall · · Score: 1, Insightful

    This is not how capitalism is supposed to work. The free market cannot deal with this situation well.

    The free market has been dealing with it, and is slowly cutting Microsoft browser marketshare down to a size where they too must adhere to standards.

    I don't see why everyone thinks a free market MUST fix everything instantly. It's all about the long term. Even when a company like Microsoft becomes dominant, you can see that over time they simply become irrelevant and other companies can eventually wear them down.

    And of course, it's not like we have a completely open market anyway - there's a lot of regulation going on in our "free" market.

    --
    "There is more worth loving than we have strength to love." - Brian Jay Stanley
  36. Re:Open standards, healthy competition, free softw by x2A · · Score: 1

    "Once upon a time, people sold browsers just like they sold any other piece of software. Netscape were making money licensing their browser for corporate environments. The web, and consequently its leader, Netscape, threatened Microsoft's desktop monopoly. So Microsoft used all the cash they had from selling desktop operating systems, bought a web browser (defrauding that company in the process) and spent lots of money developing it further"

    And now we have free and even open source browsers as well! Thank you Microsoft for taking the money out of the browser market so that we can all now download a choice of free browsers for surfin 'net with! x x

    hehe

    --
    The revolution will not be televised... but it will have a page on Wikipedia
  37. Mine is eating up 756MB by zooblethorpe · · Score: 1

    and I'm not even running any benchmarks. :)

    FF3 running with something like 45 tabs open in five separate windows. Whee!

    Cheers,

    --
    "What in the name of Fats Waller is that?"
    "A four-foot prune."
  38. Re:Open standards, healthy competition, free softw by coredog64 · · Score: 3, Informative

    Mostly correct. Netscape made money selling their horrid web server in corporate environments. They were giving the browser away for free for non-commercial users. If the truth were told, back when Netscape was a relevant browser, most of my coworkers were grabbing the free, non-commercial version and installing it at work. And Netscape didn't really care, as they were giving away their browser in order to drive sales of their server. Netscape's server arm survived for a loooong time, finally becoming the basis for Sun's application server. IIRC, only the newest version of Sun's app server (i.e. 9.x aka GlassFish) doesn't directly trace it's roots to Netscape/iPlanet. And let's not forget Netscape Directory Server. Or, as it's known today, RedHat Directory Server. During the dot-com era, it was one of the better LDAP implementations.

  39. Re:Open standards, healthy competition, free softw by geniusj · · Score: 1

    He was talking about Microsoft

  40. RegExp speed by quarrel · · Score: 1

    Does anyone know how much of a factor regular expression processing speed is to modern browser performance? What sort of sites would stress it?

    If they had better regexp algorithms, how much would it matter? (and yes, I know its a hard problem)

    --Q

    1. Re:RegExp speed by Tangent128 · · Score: 1

      I once wrote a simple wiki for fun; all the server returned was the wiki markup wrapped in a single xml tag. It used a client-side XSLT stylesheet to turn it into a fancy HTML page with the markup in the editbox (hidden, until the edit button was pressed).

      On load, a string of regexes was used to convert the markup into HTML; it also allowed previewing an edit without a server trip.
      Of course, it wasn't Google friendly at all...

  41. Re:Open standards, healthy competition, free softw by Anonymous Coward · · Score: 3, Insightful

    > gave it away for free, at a massive loss to themselves,

    Microsoft had Spyglass write IE for them and the deal was that Spyglass would get $5.00 for every copy that MS sold. MS then gave it away and thus nothing was ever paid to Spyglass.

    There was certainly no "loss to themselves".

    They did also pay various OEMs $5.00 a time to _not_ install Netscape. Or specifically it was a $5.00 discount on the price of Windows if Netscape was not installed, so that was a cost to MS.

    The former was immoral, the latter was probably illegal.

  42. The E-Penis Measure by teko_teko · · Score: 5, Funny

    By using Chrome as your preferred browser, your E-Penis will increase by a whopping 74%.

    1. Re:The E-Penis Measure by Big+Arnie · · Score: 1

      And fall off cuz of the added weight.

  43. Re:Open standards, healthy competition, free softw by centuren · · Score: 1

    I feel the same way about Android, incidentally. Now you're going to have a cellphone that's completely subsidized by another business in which the company has a virtual monopoly. And they'll be able to link their web content to their cellphone by adopting standards that the competition chooses not to (the nice thing about standards is that there are so many to choose from). They're treading a pretty fine line here, and things like the Mobile Street View working on most phones except the iPhone aren't going the help the anti-trust argument any.

    I share the sentiment, but the iPhone makes me shudder more, by iTunes tie-in alone. The mobile market needs an open OS for these "next-gen" phones, and who's got the money/motivation/ability to deliver it? Android is definitely beneficial to Google, but all optimism remains in it being beneficial to us as well.

    I suppose the best outcome might be Android's success, and a full fork that makes Google's version optional. Google's been subsidizing Firefox, after all, and that's worked out.

  44. Re:Amazingly, everyone is faster than everyone els by BZ · · Score: 2, Insightful

    Bingo. What it comes down to is that the answer to "Is X faster than Y" will depend on two things:

    1) The benchmark
    2) The day of the week (or the exact, to the minute builds you're testing, if you prefer)

    The reason for the latter is that all three are in active development. Each one is doing measurements right after landing major changes, against whatever the current state of the other two is. That means that there is inherent bias there in favor of whoever is doing the measurements being fastest: they've just hopped a step up in performance while the other two engines are on the same step they were at 3 minutes ago.

    The same thing will happen with stable releases, for what it's worth. Safari 3 shipped a faster JS engine than Firefox 2. Then Firefox 3 shipped faster than Safari 3. We'll see what the ship dates for Safari 4 and Firefox 3.1 or whatever look like, but I suspect tat if things continue as they are each will be the fastest shipping stable thing at ship time.

    Which is more or less what you said, I guess. ;)

  45. Now, how do I embed such an engine in my app? by Anonymous Coward · · Score: 0

    If Javascript is fast enough, it is a great opportunity to embed it into your applications.
    Tracemonkey/Spidermonkey does not seems to be really well documented. Besides, Yahoo thinks Javascript is the easiest to learn.
    Having used a few "scripting" languages and tested a few more like Eurphoria, Pike, Lua, CINT, etc. Anything that is not statically-typed is slow: in the order of magnitude of approximately 3X (Eurphoria) to 220X slower (Ruby /Rebol) than C/C++. Java and C# is pretty good but am still researching the possiblility of embedding the VM into my app. CPU time may be cheap, but I dont want my app to appear slow to anyone who use it. Experience is everything: no one buy faster CPU, SSD just to burn more cycles.
    BTW, Guile still won't compile on Win32 system.

  46. Why not use a JVM? by Montreal · · Score: 4, Interesting

    It's been possible to run JavaScript on a JVM for some time now (based on Mozilla's Rhino). Does anybody have any numbers as to how these recent in-browse JavaScript optimisations stack up against 10+ years of Sun work on general virtual machine optimisation? Could it be faster just to fire up the Sun JVM and use that as the JavaScript engine?

    1. Re:Why not use a JVM? by RAMMS+EIN · · Score: 1

      The work Sun did on their JVM may or may not be very impressive (I don't know), but their compiler still lacks some basic optimization techniques, which can sometimes lead to very suboptimal results. Also, the JVM is a heavyweight VM, geared towards the features of (older versions of) Java, not a general purpose VM. Getting JavaScript to run on it at anywhere near decent speed would not be trivial. Compiling JavaScript to x86 machine code is probably easier and likely to yield much better results, not to mention that it allows you to do without the bulk of a Java runtime.

      --
      Please correct me if I got my facts wrong.
    2. Re:Why not use a JVM? by multipartmixed · · Score: 2, Informative

      I don't know what the current state of the art is, but last I looked Rhino was still the fastest javascript implementation, IF you discounted the JVM start up.

      IIRC, Rhino compiles JavaScript into native Java byte code, which then gets the JIT magic sprinkled on it by the JVM pixies.

      So the quality of the Java compiler is really not all that relevant, because the code compiled by the compiler only compiles the javascript code once, making the quality of the compiler effectively order(1)... and given sufficiently large N, nobody cares about k.

      Now, a javascript->x86 compiler.. that would be interesting. Although javascript->C or javascript->gcc-intermediate would be much nicer, because I don't live in x86-land.

      --

      Do daemons dream of electric sleep()?
    3. Re:Why not use a JVM? by BZ · · Score: 1

      Faster in what sense? In addition to the "how long does it take the benchmark" number there is the "how long does it take to start up" number and the "how much memory does it use" number. Last I checked the JVMs weren't so hot on the latter two no matter how they did on the former.

    4. Re:Why not use a JVM? by ispeters · · Score: 1

      I don't have any numbers for you, but I'd be surprised if Rhino was particularly fast. I've used Rhino extensively for the last two years in a project I'm working on. The Rhino interpreter doesn't seem to do much in the way of optimization, so the JVM can't really give you any extra benefit. In fact, as far as I can tell, Rhino is just a port of SpiderMonkey to Java. This is not to say Rhino is slow--far from it. I find Rhino to be a great tool, and the speed at which it interprets scripts is "fast enough". I just don't think Sun's JVM optimizations are making a whole heck of a lot of difference.

      Ian

    5. Re:Why not use a JVM? by slamb · · Score: 1

      So the quality of the Java compiler is really not all that relevant, because the code compiled by the compiler only compiles the javascript code once, making the quality of the compiler effectively order(1)... and given sufficiently large N, nobody cares about k.

      But N is tiny. Keep in mind that while benchmark wars are fun, they aren't what users (should) care about. The purpose of these newer JavaScript implementations is to make web browsing go faster. You typically go to many, many different webpages and don't stay on them very long. Individual webpages change their JavaScript over time as well. So JavaScript is frequently compiled, used for a short while, and thrown away.

    6. Re:Why not use a JVM? by multipartmixed · · Score: 1

      Yes, but you've missed the key point. (If I understand Rhino correctly, which I think I do)

      The javascript is not compiled over-and-over again with the java compiler. Rhino is. Then Rhino emits java byte code which gets the hotspot/jit goodness.

      This means that the quality of the optimizations used by the compiler which compiled Rhino is not nearly as relevant as the quality of the bytecode emitted by Rhino, and that the quality of the JIT java bytecode thing probably dominates.

      Note, of course, that this is all speculation. I don't use Rhino nor Java.

      --

      Do daemons dream of electric sleep()?
    7. Re:Why not use a JVM? by slamb · · Score: 1

      The javascript is not compiled over-and-over again with the java compiler. Rhino is. Then Rhino emits java byte code which gets the hotspot/jit goodness.

      Wasn't the original statement that the Java compiler (used to compile Rhino) produces "very suboptimal results"? I.e., the code it produces (Rhino's JavaScript compiler) is slow. That code is executed to compile JavaScript most/all times you visit a webpage. So, if true, that's a problem.

    8. Re:Why not use a JVM? by multipartmixed · · Score: 1

      Actually, not that it wasn't slow, just that it didn't contain certain trivial optimizations. But my assumption is that once it's run a couple of times, the Hotspot code (JIT and adaptive optimizers) will have worked its magic on Rhino, so those optimizations almost certainly become moot over the long term.

      --

      Do daemons dream of electric sleep()?
  47. Apple have declared themselves evil too by David+Gerard · · Score: 2, Funny

    "Fuck it," said Steve Jobs to an audience of soul-mortgaged thralls, "we're evil. But our stuff is sooo good. You'll keep taking our abuse. You love it, you worm. Because our stuff is great. It's shiny and it works. It's not like you'll go back to a Windows Mobile phone. Ha! Ha!"

    Steve Ballmer of Microsoft was incensed at the news. "Our evil is better than anyone's evil! No-one sweats the details of evil like Microsoft! Where's your antitrust trial, you polo-necked bozo? We've worked hard on our evil! Our Zune's as evil as an iPod any day! I won't let my kids use a lesser evil! We're going to do an ad about that! I'll be in it! With Jerry Seinfeld! Beat that! Asshole."

    "Of course, we're still not evil," said Sergey Brin of Google. "You can trust us on this. Every bit of data about you, your life and the house you live in is strictly a secret between you and our marketing department. But, hypothetically, if we were evil, it's not like you're going to use Windows Live Search. Ha! Ha! I'm sorry, that's my 'spreading good cheer' laugh. Really."

    --
    http://rocknerd.co.uk
  48. Re: by CrashandDie · · Score: 0

    Uh, because Microsoft is a monopoly and Google and Apple are not?

    Wait... Google is not a monopoly? Ahahaha, nice one

  49. Dear God ... by Lazy+Jones · · Score: 1

    ... please don't let it happen that JavaScript becomes the successor of C and the browser the successor of Windows ...

    --
    "I love my job, but I hate talking to people like you" (Freddie Mercury)
  50. Re:Open standards, healthy competition, free softw by blahbooboo · · Score: 1

    What? Immoral? Uh no. More like Spyglass had crappy lawyers and/or businessmen representing them in their negotiations with Microsoft.

  51. Re:Open standards, healthy competition, free softw by Anonymous Coward · · Score: 1, Informative

    Others have pointed out that Netscape was actually making its money from server software, but you're missing the really big point: the Netscape browser was a piece of shit. I was an early Netscape user but I switched to IE because it was better.

    If MS hadn't killed Netscape the internet now would probably be dominated by two crap standards-ignoring browsers - Netscape and IE.

    Fuck Netscape, they got what they deserved.

  52. As a standalone engine? by dwarfking · · Score: 2, Interesting

    Do any of the engines mentioned in these postings offer a clean way of using JavaScript as a standalone engine for non-browser applications?

    I don't want a Java based one (don't want the JVM). I'm trying to compile V8 alone but the code has issues right now if you don't use VC++. I've tried SpiderMonkey in the past but that code is just difficult to follow.

    Interestingly under windows the WSH (Windows Scripting Host) can work with either JavaScript of VB script. The engine allows the JavaScript code to access many of the Windows objects.

    I'd like to see a JavaScript engine with pluggable modules (sort of like TCL) and possibly a nice accessible GUI (like TK).

    Any suggestions on which engine is best to use as the standalone interpreter with the easiest extensibility?

    1. Re:As a standalone engine? by multipartmixed · · Score: 2, Informative

      I know nothing of WebKit, so I will not speak of it.

      It is currently possible to use SpiderMonkey at the level of ff3 for real work. There's a bit of a learning curve, but it's totally usable. In theory, anything you write for SpiderMonkey-trunk will be usable with the new tracing stuff they've built. That's not in CVS, it's in hg (mercurial), and I'm not sure what state it's in right now. I'm guessing it's probably usable, too. Oh, I think the tracing code also requires a C++ compiler, although I could be wrong.

      > I'd like to see a JavaScript engine with pluggable modules (sort of like TCL) and possibly a nice accessible GUI (like TK).

      I have been working on something like this, and will get back it to it sooner or later. Probably early november. Unfortunately, great swaths of it is closed (it wraps trade secret libraries), but the basic infrastructure and some of the classes are open. You use it basically like any other UNIX shell interpreter.

      When I get back to this project, I plan on more rigorously defining the module loading code to make it easier to extend. Right now, it's pretty easy to compile them in, but there is no good way to load DSOs and so forth. I also want to load JavaScript-language modules more elegantly.

      If you want to see my early work -- which is not really all that useful unless you're planning on writing more classes in C to expose whatever it is you want to work with -- go here: http://www.page.ca/~wes/opensource/

      As for GUI, I don't really know anything about GUI development, but I'd totally be up for a collaboration if somebody wanted to do simple widgets. I was thinking of ripping apart Dialog for X (nee cdialog) and cloning that functionality someday.

      As of right now, I _do_ have a trivial curses interface which can put windows on a terminal, scroll output through them, and so forth. (Not in the link -- insufficient polish). I used it to put together a simple debugging environment where I type JavaScript code and it prints the results in a different window. Basically, like the debug window pair that shipped with QuickBasic 4.5.

      Oh -- and the stuff I'm working on is UNIX only. Well, it should run under Cygwin.

      I have also played with wsh under Win32. There is a lot of cool stuff you can do, although learning the win32 api appears to be a large and daunting task. I used it to write a simple remote media player for my house, where I could drag a file icon to a JavaScript program on my desktop, which spooled it to a UNIX server in the basement for pickup by a windows box in my living room which in turn would play the content through my home theatre... via another JavaScript program, using the windows media player control.

      --

      Do daemons dream of electric sleep()?
    2. Re:As a standalone engine? by dwarfking · · Score: 1

      Thanks for the link. I'll take a look at what you're doing.

      I also had looked at SpiderMonkey and one of the things about the code is that it looks like it is trying to be OO but in straight C. This is what, at least for me, makes the code difficult to work with. If I'm doing OO I prefer C++, I try to avoid doing it with macro #defines and large pointer-based structures in C.

      Nothing wrong with it (as I recall GTK was that way as well), just a personal preference.

    3. Re:As a standalone engine? by multipartmixed · · Score: 1

      > one of the things about the code is that it looks like it is trying to be OO but in straight C

      I can totally see how you would come to that conclusion. But, in my opinion that's *not* what it's doing -- it's implementing an OO system (JavaScript) in C. Subtle shade of difference, but an important one. I've written OO code in straight C, and it was far more function pointery. :)

      There are couple of things which make writing for jsapi different than your average run-of-the-mill C code.

      1. Garbage Collection: If you give memory to the JS engine, you must ensure it will be freed properly... Best analogy I can think of is writing VB4-style C DLLs. If you pass strings back to the non-C language and expect it to manage the string's lifetime, you'd better allocated with the non-C language's allocator.

      2. Finalizers: IF you write C classes for JS which absolutely cannot be managed by the garbage collector, you need to write a finalizer for the GC to call

      3. What you're writing will usually be a method for a JS object. That's not really relevant to OO-ness from the C point of view.

      4. If not a method, it'll probably a getter/setter. Which I consider to be equivalent: prop/method==false dichotomy.

      Oh - I just had another analogy -- writing jsapi code for spidermonkey is virtually equivalent to writing JNI code for java. Actually, I'll bet you could make jsapi bindings for cxxwrap or swing. Not that I think that's a good idea.... simply wrapping system libs sucks, I prefer to think them through and create modules with a true javascript-flavour-idiom-blahblahblah.

      The other references you've made sound like you've had a look through some of the engine itself, rather than trying to use the API implemented in jsapi.h. I'd... ah, not recommend doing that, unless you're trying to learn "cool tricks". And there are bunch of them in there! But you don't need to read any of them to do productive work.

      Also, most of the crazy macros you see coming out of there? You can ignore them and use JS_* functions defined in the API and defined on developer.mozilla.org. MOST of the macro-laced code requires "private knowledge" to prove correct and saves only on function call overhead. Personally, I don't need speed anywhere as bad as I need solid code, so I don't use 'em unless it's impossible not to (rarely if ever) or the profiler tells me I need to (hasn't happened yet).

      So, ah. Last two paragraphs in summary: jsapi - good. Internals of spidermonkey - highly optimized at the source-code level. Not good reading, also makes maintenance a challenge.

      (for anyone familiar with jsapi reading this -- bz? -- the macro stuff I mentioned, I mean things like the difference between JSVAL_TO_STRING(vp) vs. JS_ValueToString(cx, vp)... They are equivalent in all outside-of-the-interpreter cases, except maybe the branch call back [cx not in rt?], IF vp is a jsstring, ignoring the function call overhead. But if vp is not a jsstring, the behaviour is NOT consistent with what I think non-spidermonkey-maintaining-programmers would expect)

      --

      Do daemons dream of electric sleep()?
  53. Don't use Noscript! by YA_Python_dev · · Score: 2, Insightful

    JavaScript in Firefox is (almost?) never the source of security problems in the real world. If Noscript stops something is only because an exploit in another component also uses JavaScript (and often only because the person writing the exploit code was lazy).

    Try disabling Java and deinstalling Flash and all the plugins (or at least using Flashblock) and Adblock Plus+Easylist. You will achieve exactly the same results.

    I'm a web developer and I'm asking to please don't disable JavaScript. It's not a security problem per-se if you keep your browser updated and in fact makes the web *less* safe because encourages legitimate web developers to use much worse alternatives, like Flash.

    --
    There's a hidden treasure in Python 3.x: __prepare__()
    1. Re:Don't use Noscript! by RiotingPacifist · · Score: 1

      Flashblock is not secure, it can be got around with object tags, its a nuisance blocker not a security tool. TBH i wish there was a security aware plugin blocker as Noscript is just too much of a PITA to use

      --
      IranAir Flight 655 never forget!
    2. Re:Don't use Noscript! by svank · · Score: 1

      I'm a web developer and I'm asking to please don't disable JavaScript. It's not a security problem per-se if you keep your browser updated and in fact makes the web *less* safe because encourages legitimate web developers to use much worse alternatives, like Flash.

      NoScript blocks flash, too.

      Don't worry about NoScript users when you're making web pages. Very few people use NoScript (I assume). Those of us who do use it have intentionally disallowed your scripts. If we decide we want your scripts to run, we'll temporarily allow them on your domain. Otherwise, bug off. You've got no business trying to override our decisions in our browsers.

  54. How about rendering speed by Anonymous Coward · · Score: 0

    On my quad core machine I've got logitech mx620 mouse which scrolls very accuratly so i have set one "tick" of scroll wheeel is one line annd it barely heaps up wyth rendering speed on firefox on chrome a bit better until i fire up some download then it becomes more sluggish than firefeox wit multiple tabs loading and downloadin files. on dual core laptop scroll is too very sensitive and i would like to think that dual core machine would keep up with scrolling but it doesn't. and while this is a bit inconvinient scrolling on my asus 901 in firefox is pain in chrome works quite well but when download stars it is imposiible to use the browser. I mean nice that java script speeds that can make huge difference on webapp style pages but scrolling shpuld be fast and accurate.

  55. Re:Amazingly, everyone is faster than everyone els by Flammon · · Score: 1

    All the open source projects are benefiting from each other at an amazing rate with healthy competition. I'm anxious to see how well Microsoft will do in the end, all alone without the ability to use anyone else's code.

  56. And thus begin... by anno1602 · · Score: 1

    the JavaScript engine wars.

    1. Re:And thus begin... by multipartmixed · · Score: 1

      Suits me fine - Bring it On!

      I started a major JavaScript-engine-using project over a year ago.

      Boss said: are you sure it will be fast enough?
      I said: Between Moore's law and the javascript performance increase that's due, I'm sure it will be.

      (Note that at the time ActionMonkey had just been announced, it was a pretty safe bet it woulda arrive)

      So far, so good. Another 8 months or so and I should have a product. And it's already in the right performance neighbourhood *without* all this cool new stuff.

      --

      Do daemons dream of electric sleep()?
  57. Re:Amazingly, everyone is faster than everyone els by BZ · · Score: 1

    These projects aren't using each other's code, really. Not for the JS engine.

    And all three JS engines are under licenses that would allow Microsoft to use them if so desired (BSD, BSD/LGPL and MPL/GPL/LGPL).

  58. BORING by Anonymous Coward · · Score: 0

    GASP

  59. Re:Open standards, healthy competition, free softw by Anonymous Coward · · Score: 0

    You say "now that browsers are a commodity" like that fact isn't linked to IE being released for free. I'd say browsers are a commodity strictly BECAUSE Microsoft made them so.

    I also find it funny that Slashdot talks about commoditizing software as a horrible thing when it comes to web browsers in 1995 but as somewhere between inevitable and a moral imperative for OSs (Linux) and other software now.

  60. Re:Open standards, healthy competition, free softw by Anonymous Coward · · Score: 0

    Once upon a time, people sold browsers just like they sold any other piece of software. Netscape were making money licensing their browser for corporate environments. The web, and consequently its leader, Netscape, threatened Microsoft's desktop monopoly. So Microsoft used all the cash they had from selling desktop operating systems, bought a web browser (defrauding that company in the process) and spent lots of money developing it further. Then they gave it away for free, at a massive loss to themselves, to "cut off Netscape's air supply". Still, that wasn't enough to unseat Netscape, so Microsoft went further and bundled it into their operating system too. Now all of a sudden 95% of the people on the planet had Microsoft's browser whether they liked it or not - and Netscape were basically dead.

    Microsoft were able to eliminate the competition not because they offered a better product, but because they had a dominant position in another market and were willing to dump their product on the market no matter the cost, to put another company out of business. This is not how capitalism is supposed to work. The free market cannot deal with this situation well. The invisible hand is tied behind its invisible back. So in many countries, abusing a monopoly position in this way is illegal. And that's why Microsoft is vilified here - because they acted like bullies, took something dear to geeks, and shat all over it to make money.

    Now that browsers are a commodity, how are Apple and Google harming the browser market with anticompetitive actions? Answer - they aren't. They are actually competing by providing better products. And that's why it's completely different to what Microsoft did.

    Ahh.. this is the reason I still read Slashdot comments. I love it when people pretend to have a clue. So much is left out from this rant you copied and pasted from some linux fanboy dot com web site that I wouldn't know where to start. Could you set up an RSS feed so I can read your humorous, kiddie, fan boy, copy and paste rants without having to dig around for them?

  61. Javascript/Tk by argent · · Score: 1

    As for GUI, I don't really know anything about GUI development, but I'd totally be up for a collaboration if somebody wanted to do simple widgets. I was thinking of ripping apart Dialog for X (nee cdialog) and cloning that functionality someday.

    There are already Tk bindings for Scheme and Perl as well as Tcl, why not implement Javascript/Tk and avoid all the heavy lifting?

    1. Re:Javascript/Tk by multipartmixed · · Score: 1

      > There are already Tk bindings for Scheme and Perl as well as Tcl, why not
      > implement Javascript/Tk and avoid all the heavy lifting?

      In principle? No reason, other that it had never crossed my mind.

      Like I said, I'm not a GUI guy. :)

      Somehow, I have managed to avoid GUI work for years and years and years and years... I've done GUIs with VB4, lots of web apps, I wrote an X widget once in school... But holy moly that was a long time ago.

      On paper your proposal makes a LOT of sense. In fact, the bindings for Lua and REXX will probably provide significant guidance.

      Hmm. Thanks!

      --

      Do daemons dream of electric sleep()?
    2. Re:Javascript/Tk by argent · · Score: 1

      You're most welcome. I've long thought Javascript has been a much maligned language and have sorely felt the lack of a good command line Javascript... combined with Tk, well, I look forward to what you come up with most eagerly.

      No reason, other that it had never crossed my mind.

      Why, then, I am answered. Goodness knows that's a common situation, there's so much out there now that nobody can keep track of it all. I only recently discovered m0n0wall, after years of building my own FreeBSD-based firewalls by hand.

      Somehow, I have managed to avoid GUI work for years and years and years and years...

      Me too, the last time I did major GUI work was when I wrote Workbench for the Amiga. Most since then has been in Tcl/Tk, and why that is so easy it is hardly work at all. :)

      But wait, you mention REXX? I wasn't aware that was still in active use, outside the mainframe world... and surely nobody is writing GUI software on mainframes.

    3. Re:Javascript/Tk by multipartmixed · · Score: 1

      > I've long thought Javascript has been a much maligned language and have sorely felt the
      > lack of a good command line Javascript... combined with Tk, well, I look forward to what
      > you come up with most eagerly.

      You might have to wait a while -- but I'll have something eventually. GUI isn't on the paid-to-develop project plan, but most of the other important bits are. Which is great, I'm getting paid to write software I'd write for free if I could afford to do so. (Shhhh! Don't tell anybody! ;)

      > Me too, the last time I did major GUI work was when I wrote Workbench for the Amiga

      Did you just say you wrote Workbench for the Amiga? Uhm, listen.. if you're ever in my neighbourhood, ah, dinner's on me.

      > But wait, you mention REXX? I wasn't aware that was still in active use, outside the mainframe world..

      Those crazy OS/2 guys. You can kill their OS, but not their spirit. :)

      I haven't written anything in Object REXX (yes, you heard that right) but it looks like a pretty decent language. One of the guys I work with was heavy in OS/2 until just a couple of years ago.

      Me, I haven't actually used REXX since the VM/CMS days. And back then.. I didn't know enough to appreciate it.

      --

      Do daemons dream of electric sleep()?
    4. Re:Javascript/Tk by argent · · Score: 1

      Which is great, I'm getting paid to write software I'd write for free if I could afford to do so.

      I love that kind of job. Though I've found it does change the focus of what I'm working on, too.

      Did you just say you wrote Workbench for the Amiga?

      Yeh, I quit working on it after most of the features of Workbench got picked up by the regular Amiga Desktop in 2.0... didn't see much point after I wasn't even using it any more. There was a "Workbench II" that was more of a Norton Commander clone, but I didn't have anything to do with that.

      Only time I used REXX was on the Amiga. I got kind of turned off by the weird way it treated uninitialized variables, but that may have been an AREXX quirk.

    5. Re:Javascript/Tk by argent · · Score: 1

      Did you just say you wrote Workbench for the Amiga?

      You know, it really sucks when you can't even remember the name of your own software after 20 years.

      I wrote a replacement for the standard Amiga Workbench. I just googled for it, and realize that I got mixed up. My replacement was originally going to be called "The Programmer's Workbench" but I shipped it as "Browser". It used the same basic layout, operations, and files as Workbench, but wasn't restricted to showing icons... it showed all files (not just files with icons) and file details, and had a file dialog that let you open folders and files by name. It went out on one of the Fish disks, and I quit maintaining it after AmigaDOS 2.0 came out because they incorporated most of the features of Browser in Workbench 2.0.

  62. i did some number-crunch tests - it's a lot faster by cathector · · Score: 2, Informative

    i have a page which does some numerical simulation in javascript,
    essentially an O(N^2) finding-nearest-neighbors-in-two-dimensions thing,
    and here are some trials w/ 2000 points, on an x86 windows machine:

    Safari 3.1.2          - ~50 seconds, maybe more
    Safari 3.1.2 + Webkit - ~10 seconds
    Firefox 3.0.2         - ~22 seconds
    Chrome 0.2.149.30     - ~19 seconds

  63. Re:Open standards, healthy competition, free softw by Anonymous Coward · · Score: 0

    need I remind you that IE4 was a much much better browser than netscape's at the time? If it had sucked or netscape was better then people would have used netscape. I used to try to use netscape and gave up because it sucked so much.

    Microsoft did offer a better product, and they did so at no extra cost.

    And yes, it pains me to say it :(

    I'm really looking forward to having webkit in epiphany :)

  64. Re:Open standards, healthy competition, free softw by Anonymous Coward · · Score: 0

    Microsoft were able to eliminate the competition not because they offered a better product

    uhhhh it WAS the better browser of the time.

    It didnt crash every other site. It didnt lock up randomly, the java (BUILT IN not downloaded) was faster. It rendered pages faster. plugins were easy to make (activex).

    Now looking back at it some of those things were not as good as we thought they were (looking at you activex).

    Yeah everyone just jumped at IE because netscape was such a better product. Lets face it netscape was flakey. IE was just *less* flakey than netscape.

    Also by your very logic. Apple and Google are giving it away. Soooooooooo if it is a better product why are they not charging for it? Especially Apple they nickel and dime you for everything. They are doing the SAME thing. Better product at 0 cost? How are they NOT dumping? Apple even tried to tie it to iTunes and people reacted rather negatively. And what will be the built in browser for the next OSX?

    Do not buy into the groupspeak that everything MS does and everything everyone else does is good. MS learned from Apple, IBM, Oracle, and others.

  65. What's next? by itayperl · · Score: 1

    Next week: NullJS v0.5beta!

    Sends all your JS hacks to /dev/null.

    Runs SunSpider in 2 ms!
    472% faster than SquirrelFish,
    640% faster than V8,
    732% faster than TraceMonkey!

  66. A question for anyone in the know . . . by Cyberllama · · Score: 1

    Does anyone know if this means that, eventually, the iPhone might benefit from this performance improvement? I was under the impression that Safari was webkit-based but I don't know if that includes Mobile Safari or not. Anyone know?

  67. Re:Open standards, healthy competition, free softw by whong09 · · Score: 1

    So as someone who still hasn't formed an educated opinion on this subject, I'd like to ask: what made Microsoft so evil?
    As far as I can tell, Microsoft is only guilty of forcing its way into a market that was previously dominated by Netscape by handing away its browser application for free. They also bundled their browser onto their operating systems to further get people to use their product over Netscape's. However, at the same time Netscape gave out their non-commercial client browser for free as well. Also, there was nothing stopping Netscape from running on the Windows operating system at the time. Thus a consumer at the time using Windows had the choice of either bringing Netscape onto their OS (at no charge to them) or using the native IE that came with the OS.
    What I fail to understand though, is why IE won out in the end. If your claim is true, that IE was an inferior product thrown together to drive Netscape out of business, I cannot perceive why the consumer would choose such an inferior product over a superior one that costs the same thing. Perhaps there's a convenience factor involved, but even still, that shouldn't be enough to give Microsoft the monopoly that it established.
    Also there are commenters below who claim that IE was actually the better product and support that claim with details on how IE was better. Please explain why you claim that Netscape was better. Citations would help your rebuttal.

  68. Re:Open standards, healthy competition, free softw by fermion · · Score: 1
    When the World Wide Web was created by stitching together a bunch of very clever technologies, life was good, and we all mostly used mosaic, though a few broswers predated it. We were happy. Then netscape created an innovative way to look at web content, called netscape navigator. It was on of many commercial entries, and coincided with the opening of the web to personal and commercial interests, away from the academic focus. Netscape was good, and along with other browsers, made the OS you were using unimportant.

    This, of course, worried MS, so they bought a web browser and tightly integrated with their MS Windows Desktop. This did three things. First, it made the WWW a MS product, as many sites would now only run on MS Windows. Second, it allowed a much tighter control over presentation, which broke the HTML standard that focused on context tags, not presentation. Three, much like the DOS days where MS put most third developers at a great disadvantage by limiting information, Netscape was not able to compete and keep a OS neutral product.

    This caused netscape problems, and while many of us who were not slaves to MS continued to use it, many thought netscape was inferior because it properly and rightly broke when put forth with substandard programming the MS encouraged. Truth be told, as Netscape lost market share, the browser itself became in fact bad, and the death was likely a good thing.

    By that time everyone used IE, and the web was broken, apparently beyond all hope. It took about 5 years to fix it. Several technologies that allowed the compulsive types to impose look and feel, like flash and CSS, helped this trend. The emergence of Scandanavia and western europe as serious player in the software game also helped. Google, as well as web retailers in general, pushing for maximum customer base, developed other technologies that rendered the IE hacks much less crucial. The key though was the commodization of the web engine, which meant that most of use one of a small set of engines, with the notable exception of IE and Opera.

    The thing is that the new web war is moot. As long as MS has a desktop monopoly, they will abuse it by tying IE and pushing customers to related assets. Google is going to have a hard time leveraging it's essential search monopoly to making customer use a special web browser to access content. Perhaps in certain enterprise setting, but what enterprise is going to release ownership of sensitive data.

    In any case, the new game in town is virtualization, and this provides a method to wean customers away from MS as well as provide the central control and distribution of big iron while retaining the benefits of the microcomputer. Given that virtualization implies that the current OS is flexible, one might assume that a browser that runs on any OS, like Firefox, or Opera, or even Safari if Apple can get it up, will be the browser of choice.

    --
    "She's a scientist and a lesbian. She's not going to let it slide." Orphan Black
  69. Re:Open standards, healthy competition, free softw by sco08y · · Score: 1

    I was an early Netscape user but I switched to IE because it was better.

    That's absolutely true. I recall coding for IE 4 vs. NS 4. There was no comparison, you could actually *do* things with IE 4. NS 2 and 3 were great but the engine assumed the page would load in a linear manner. NS's own hacks blew this model up and they never reworked it. By the time the layer and ilayer tags came around, the engine was collapsing under its own weight.

  70. Re:Open standards, healthy competition, free softw by samkass · · Score: 1

    But with Android it goes beyond the phone. Word is that the Google App Store is going to be completely free for developers. Google will host, ship, clear, etc. In essence, it will be subsidized by Google's existing server infrastructure. Apple would have a really hard time competing with that.

    --
    E pluribus unum
  71. Re:Open standards, healthy competition, free softw by gordo3000 · · Score: 1

    so in other words, thank god for MS??

    you make it sound like they did something bad. if it wasn't for them, we'd be stuck paying for browsers and netscape would be a monopoly. good job MS, running a profiteering company into the ground so a better product and lower prices can make it to the consumer.

    I"m not sure why you are complaining. you applaud google and apple and mozilla for competing and providing a "commodity" product but hate the company that started the revolution of commodity web browsers. can you believe you used to pay for something equivalent to a better JS engine over the "freer, slower" version? w/o MS few could imagine a world where companies expended tons of resources to give away a product to increase it's footprint.

    I'm glad they drove that waste of space netscape into the ground. it may have stagnated browser development for a few years, but it created the environment for a far more robust browser market than ever before (and it's all FREE).

  72. WebKit added Selectors API a while ago by ftekkie · · Score: 1

    WebKit added W3C Selectors API early this year so it makes a reasonable milestone in the development. It's no coincidence Google chose WebKit core for the Chrome.