3 ms·

What are we to do? We build data visualization software, but firefox is REALLY slow at rendering SVG (so no d3 for us). We have a choice of asking our customers

by myrryr 12y ago

What are we to do? We build data visualization software, but firefox is REALLY slow at rendering SVG (so no d3 for us). We have a choice of asking our customers to run ie11 or chrome, since both run quickly. We would recommend firefox, since we really like the Mozilla foundation, but the performance of it is so bad we have to steer people away from it. It is a sad state of affairs.

GlennS 12y ago
I'm a little surprised by this. I can believe that Firefox is slower (I haven't done the comparison myself), but even so it's still capable of rendering hundreds of thousands of points or thousands of complicated geometric shapes. I would have thought it you had more data than that then the points will all be rammed together and hard to distinguish, so it would be better to switch to density plots.
- shangxiao 12y ago
  I've also noticed it slower on an SVG based app. Not terribly slower, just enough to make it look slightly glitchy compared with the smoothness of Chrome with interactive actions like drag n dropping components around.
deleted 12y ago
[deleted]
lucb1e 12y ago
If you make software (which people want to use, of course) and notice a mainstream open source browser (in this case Firefox) being slow at something in particular, wouldn't it be advantageous to you and everyone else if some of you could briefly look under the hood to see what the problem is? Maybe not fix the bug, but at least let Mozilla know that there is a pain point somewhere (perhaps with specific source files or functions which take forever). Probably gets it fixed much faster as when you just keep using Chrome and disregard Firefox completely.
- shangxiao 12y ago
  Have you ever "looked under the hood" ? Browsers aren't your average weekend open source project, they're behemoths :) I once checked out chromium in order to test out whether file writing would be easy to do. The size of the project alone meant it took me forever to find out where to patch it. (Edit: This was something like 5 years ago before I started to grow a distaste for Chrome)
  - Silhouette 12y ago
    Have you ever "looked under the hood" ? Browsers aren't your average weekend open source project, they're behemoths I've sometimes wondered whether the barrier to entry is the biggest thing holding back FOSS. I'm an experienced developer, quite capable of diving into the kind of code these projects run. Now and then I have enough spare time that I might be able to make a useful contribution. I would be happy to support some of these projects in the spirit of giving something back. Every single time I look at a major FOSS project where I'd like to help, the very first thing I run into in the developer documentation is an installation/build process a mile long with absurd overheads. Large FOSS projects often require a whole set of custom tools. Many don't comply with normal conventions on the host OS; I'm on Windows, and assuming every developer in the world runs Linux is a particularly common problem. Quite a few require installation of a specific version of a certain compiler toolchain. I understand that portability is difficult. I've worked on projects that had to be compiled on many different platforms. I've worked on projects that had to be cross-compiled from one platform to run on another. The issues raised by these environments aren't trivial. Even so, I have never worked on a successful professional project that managed to make things as complicated as large FOSS projects almost always do. And while I'm happy to help out if I can, I simply don't have time to ensure that I've got this week's project's specific preferred version of a VCS, Bash, GCC, and so on installed so they clutter my standard file system, environment settings, registry, editor/IDE preferences, and all the other things that any developer surely wants as clean and tidy as possible while they work.
    - lucb1e 12y ago
      > Large FOSS projects often require a whole set of custom tools. I was about to say that for the two projects I've tried this with, Filezilla and Firefox, it was actually quite reasonable. Especially Firefox, given its size, was surprisingly simply even if compiling took longer than I thought. But then I read you are on Windows. Yeah, that's hell. I tried a few hours on Filezilla before deciding that it's just too messed up.
dblohm7 12y ago
Have you filed any bugs for it?

by myrryr 12y ago

GlennS 12y ago

I'm a little surprised by this. I can believe that Firefox is slower (I haven't done the comparison myself), but even so it's still capable of rendering hundreds of thousands of points or thousands of complicated geometric shapes. I would have thought it you had more data than that then the points will all be rammed together and hard to distinguish, so it would be better to switch to density plots.

shangxiao 12y ago
I've also noticed it slower on an SVG based app. Not terribly slower, just enough to make it look slightly glitchy compared with the smoothness of Chrome with interactive actions like drag n dropping components around.

deleted 12y ago

[deleted]

lucb1e 12y ago

If you make software (which people want to use, of course) and notice a mainstream open source browser (in this case Firefox) being slow at something in particular, wouldn't it be advantageous to you and everyone else if some of you could briefly look under the hood to see what the problem is? Maybe not fix the bug, but at least let Mozilla know that there is a pain point somewhere (perhaps with specific source files or functions which take forever). Probably gets it fixed much faster as when you just keep using Chrome and disregard Firefox completely.

shangxiao 12y ago
Have you ever "looked under the hood" ? Browsers aren't your average weekend open source project, they're behemoths :) I once checked out chromium in order to test out whether file writing would be easy to do. The size of the project alone meant it took me forever to find out where to patch it. (Edit: This was something like 5 years ago before I started to grow a distaste for Chrome)
- Silhouette 12y ago
  Have you ever "looked under the hood" ? Browsers aren't your average weekend open source project, they're behemoths I've sometimes wondered whether the barrier to entry is the biggest thing holding back FOSS. I'm an experienced developer, quite capable of diving into the kind of code these projects run. Now and then I have enough spare time that I might be able to make a useful contribution. I would be happy to support some of these projects in the spirit of giving something back. Every single time I look at a major FOSS project where I'd like to help, the very first thing I run into in the developer documentation is an installation/build process a mile long with absurd overheads. Large FOSS projects often require a whole set of custom tools. Many don't comply with normal conventions on the host OS; I'm on Windows, and assuming every developer in the world runs Linux is a particularly common problem. Quite a few require installation of a specific version of a certain compiler toolchain. I understand that portability is difficult. I've worked on projects that had to be compiled on many different platforms. I've worked on projects that had to be cross-compiled from one platform to run on another. The issues raised by these environments aren't trivial. Even so, I have never worked on a successful professional project that managed to make things as complicated as large FOSS projects almost always do. And while I'm happy to help out if I can, I simply don't have time to ensure that I've got this week's project's specific preferred version of a VCS, Bash, GCC, and so on installed so they clutter my standard file system, environment settings, registry, editor/IDE preferences, and all the other things that any developer surely wants as clean and tidy as possible while they work.
  - lucb1e 12y ago
    > Large FOSS projects often require a whole set of custom tools. I was about to say that for the two projects I've tried this with, Filezilla and Firefox, it was actually quite reasonable. Especially Firefox, given its size, was surprisingly simply even if compiling took longer than I thought. But then I read you are on Windows. Yeah, that's hell. I tried a few hours on Filezilla before deciding that it's just too messed up.

dblohm7 12y ago

Have you filed any bugs for it?