3 ms·
I tried the new Firefox and it is very fast, at least for some things. I'm working on a side project that really taxes the browser so I occasionally will test o
by gpsx 9y ago
I tried the new Firefox and it is very fast, at least for some things. I'm working on a side project that really taxes the browser so I occasionally will test on the other browsers. The old firefox was very slow for my UI where I would drag things around. Now it is very nice. Maybe better than Chrome. But I do have a few problems. This is too bad because all things being equal I would prefer to use Firefox. So the problems...
First of all I am working on a windows machine. The standard UI elements on Firefox are incredibly ugly, as in they look like something from a java application 15 years ago. That is enough reason for me not to use it. Edge looks the best and Chrome is only very slightly behind.
Secondly, the project I am doing is a sort of programming environment. The debugger on Firefox is not working right for some reason. I am debugging dynamic code (as in code that is not loaded from a source file but instead entered by the browser user). So when I when I tried using Firefox I quit becauseI couldn't debug the code I was writing in the app.
The last reason I don't want to use it may not be a great on but I'll say it anyway - the rendering is a little different between Chrome and Firefox. That maybe Chrome's fault. I think I fixed most cases in my app, but I still have errors of a few pixels. In my particular case I am probably going to target Electron also (or even exclusively) so it makes sense to work more in Chrome.
Just to add some additional info, Edge works really well. In most cases it uses render rules more like Firefox, which is what makes me thing Chrome is the problem there. The main problem I have with Edge is that it works really well until it crashes. I can really tax the browser if I am working with a lot of data and Edge seems to die the fastest.
My main conclusion is that the Firefox team did some great things, but it is going to take more work to really get it to be an all around better or even equal browser. That will be a tough task but I would like to see them do that.
- romwell 9y ago>First of all I am working on a windows machine. The standard UI elements on Firefox are incredibly ugly, as in they look like something from a java application 15 years ago. Perhaps you are using a version of Windows from 10 years ago? It just isn't the case on Windows 10 - looks great (it uses the system UI elements). >Secondly ... the debugger on Firefox is not working right for some reason. You mean the debugger in the web-based programming environment that you are developing on is not working in Firefox? Is that a fault of the browser? >The last reason: the rendering is a little different between Chrome and Firefox. >My main conclusion is that ... it is going to take more work to really get it to be an all around better or even equal browser. One of your criteria is that Firefox has to be literally Chrome in the way it renders things. I don't think you'll ever be satisfied with it (unless you change your mind). It's already a better browser for my use case: leaner, faster, and has Reader View button in the UI out of the box, which is great in general, but more so if I'm at work. Thanks for sharing your experience, though! I hope that you project ends up working fine in FF as well :)